Allow edits to chants with no existing full text; fix browse source dropdown #1716
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.
Use
Source.short_heading
in dropdown on the Browse Chants view.Adjust requirement for a chant to have a non-empty
manuscript_full_text_std_spelling
field. This PR maintains the requirement for this field to be filled out on chant creation. On chant edit, a chant can be saved with an emptymanuscript_full_text_std_spelling
field iff that field was already empty. This allows necessary edits to other fields (e.g., changing a genre, feast, or service designation) without necessarily having to locate the full chant text.Closes #1696. Closes #1715.
Refs #1713: Moves folio-sequence uniqueness check to the
ChantCreateForm
rather than theChantCreateView
. Also adds this check to theChantEditForm
(previously this was not checked at all on chant edits).