For example, there's a bug on Kybern.org where you get an error if your group description is too long. The allowable length of the description is specified on the Django model, and I forgot to include that information in both the state change and, eventually, on the front end.
It should be easier for developers to have consistent validation throughout the stack. The two key questions I see are:
how to automatically check for model constraints in a state change
how to structure state change validation constraints such that they can be easily displayed on the front end
Recently: had a couple bugs due to state change fields not matching up to permissioned model fields; need to find an approach that prevents those kinds of manual errors. Bumping up the priority.
For example, there's a bug on Kybern.org where you get an error if your group description is too long. The allowable length of the description is specified on the Django model, and I forgot to include that information in both the state change and, eventually, on the front end.
It should be easier for developers to have consistent validation throughout the stack. The two key questions I see are: