You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 30, 2024. It is now read-only.
We got a support issue today, the user couldn't publish her visualization. I tried from the console, it rolled back when calling save on the Visualization object. After renaming it, saving worked.
Looking at the code very briefly, it seems the name must be unique for a given user's visualizations. But it wasn't a problem when they were unpublished. Why didn't validates_uniqueness_ofAPI complain when the object was created? 🤔
The text was updated successfully, but these errors were encountered:
How did she manage to create visualizations with the same name?! Because I tried and I couldn't: duplicating a viz adds a "Copy of" to the title, and if I try to rename it afterwards, the change just gets ignored. And the app doesn't let you create a visualization with a name that already exists. 🤷♂️
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We got a support issue today, the user couldn't publish her visualization. I tried from the console, it rolled back when calling
save
on theVisualization
object. After renaming it, saving worked.Looking at the code very briefly, it seems the name must be unique for a given user's visualizations. But it wasn't a problem when they were unpublished. Why didn't
validates_uniqueness_of
API complain when the object was created? 🤔The text was updated successfully, but these errors were encountered: