Render an extra empty formset for a schema definition if none exist #172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #170.
This is a UX improvement for the schema management form. Previously, when creating a new schema, the form would initialize without an empty formset item for a schema definition, like this:

This is a little confusing and annoying because at least one schema definition is required for all schemas, a requirement that was easy to miss without the fields present initially. If the user does manage to notice before submitting the form, they'd understandably wonder why we were forcing them to click "Add schema definition."
With this PR, we initialize the schema management form with an "extra" empty formset item when there aren't any

SchemRefsfor the schema, as in the case of a new schema. That way the form will initialize like this:Users can still remove all the formset