-
Notifications
You must be signed in to change notification settings - Fork 157
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
Warn about forms with old version of entity spec <2024.* #730
Comments
We've discussed that it'd be nice not to outright reject forms like this if doing so is not necessary. Instead, we can warn users if the form definition they've uploaded specifies an old spec. I'll update the description above. Surfacing the warning in Frontend will probably require changes to Frontend. I've added the frontend label to the issue. I've also removed the documentation label, since it isn't a docs issue. There's an issue at getodk/docs#1855 to update user docs, and an issue at getodk/central-backend#1211 to update API docs. Feel free to edit those! |
Should the warning about the old spec appear only when a user adds a new or also when adds a new version of a form (e.g changing the new spec to the old spec), undeletes the old spec form? |
When we migrate the entity form spec in existing entity forms we will
not want to acceptwant to warn about new forms with an old entity spec.From the above issue:
UPDATE: The issue mentioned rejecting form definitions, but we've decided to show a warning about them instead.
One hurdle users might encounter is if they have an old version of their form in XML and it has an old entity spec version. In that case, we can give users info on how to recover (e.g. download upgraded XML, look at spec to figure out changes to apply).
The text was updated successfully, but these errors were encountered: