Let users set is_microsetta when creating a project but not alter it when updating #59
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.
As @wasade points out, if an existing project has at least one existing kit, reclassifying that project from being a Microsetta project to not being one (or vice versa) requires some actions on the ag_kit and ag_kit_barcodes tables. The existing update_project functionality does not take these actions (and I am not entirely clear on what they should be), so in the short term, disable changing the is_microsetta field through the microsetta-admin gui when UPDATING a project's info. However, continue to allow setting this info through the gui when creating a NEW project.