Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure that there are no collisions between charts at /grapher/ and Mdims at /grapher/ #4029

Open
Tracked by #3874
danyx23 opened this issue Oct 7, 2024 · 0 comments
Labels
needs discussion ops Devops related issues (stagings servers, ...) priority 2 - important viz

Comments

@danyx23
Copy link
Contributor

danyx23 commented Oct 7, 2024

Under the /grapher/ path on our website so far we had charts (what we now often call "standalone" charts) and redirects to charts. With MDims we now have another "thing" that lives under this url-space. Because of this /grapher/poverty could either be an mdim or a standalone chart. We should either decide on a naming scheme to discern these or add a safety mechanism (maybe trigger based in the DB?) to make sure that we don't have different entities with the same slug.

@danyx23 danyx23 changed the title ensure no collisions between charts at /grapher/ and mdims at /grapher/ Ensure that there are no collisions between charts at /grapher/ and Mdims at /grapher/ Oct 7, 2024
@danyx23 danyx23 added viz ops Devops related issues (stagings servers, ...) labels Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs discussion ops Devops related issues (stagings servers, ...) priority 2 - important viz
Projects
None yet
Development

No branches or pull requests

2 participants