For the CfP, we do a lot of changes to the fields that are meaningful, based on the state of the proposal. It'd be nice to pop up, when editing in the admin pages, when fields will become unused/overwritten, or are now required.
This could be done by having different subclasses, but that means we'll have subclasses for type as well as state. Maybe it's cleaner to have a way to mark up fields within a class as only applying to certain states.
For the CfP, we do a lot of changes to the fields that are meaningful, based on the state of the proposal. It'd be nice to pop up, when editing in the admin pages, when fields will become unused/overwritten, or are now required.
This could be done by having different subclasses, but that means we'll have subclasses for type as well as state. Maybe it's cleaner to have a way to mark up fields within a class as only applying to certain states.
See also #679.