-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
feat: topo data API #389
Comments
Do you have some sample data so that we can figure out how to store/retrieve it in the backend? |
Yep. Here you go |
I would think we can just store it as a string. The paper import function works with a string and the export function returns a JSON object or string. See http://paperjs.org/reference/path/#exportjson |
do you expect the internal structure to change? Another word should we store a version number along with the data? |
I think its likely to change structure, especially as we implement new features. A version number seems like a good idea. Although the version could also be put into the topo data itself, which might be better? |
Sure. We can make it an internal field for now. The version can help the frontend rendering code differentiate changes. |
We need the ability to to assign and retrieve a JSON object to photos/photo tags for the topo feature
The text was updated successfully, but these errors were encountered: