awkward behavior when editing object types

[gnomicosuw]

1. Auto-correcting behavior

• When editing an object type, the inputs do not auto-correct. This is different than editing sample types, where the inputs do auto-correct.
• For example, if you try to delete the name of a sample type it reverts back to the old name, but if you try to delete the name of an object type it throws an error in the GUI

NOTE: For now I am setting up the backend to auto-correct the inputs on the object types so that the behavior is consistent with the sample types. We can change this later, but it will mean changing the front-end, too (in order to process the errors when submitting the form). And for now we can simply re-use the same templates that have been created for updating a sample_type.

2. Rows & columns
   • rows and columns only apply if the handler is “collection”, but the fields do not automatically show/hide in the GUI when you edit the handler. This is very awkward. In order to set the rows and columns you have to change the handler to a collection, save the item, then re-edit it to see the “rows” and “columns” fields (*)
   • rows and columns can be negative in the GUI. (Haha, I’d like to see that in the lab!) Interestingly, the GUI automatically sets them to [1,12] if you try to make them zero or blank, but it allows you to put in negative numbers.

() NOTE: By comparison, the “sample type” only applies if the handler is “sample_container”. Unlike the rows and columns, this field does * automatically show/hide when you make the handler to “sample_container”. (this is good!)

Here is a screenshot with negative rows, columns

3. handler can be blank.

• the “handler” can be blank. I'm not sure whether we want that?

Here is as screenshot of what happens with a blank handler (you get a blank option in the left-hand column)

[marikoja]

Design notes per conversation with @spcoon

• Add header to sidebar `Object Categories
• Replacing terminology of Containers and Handler with Object Category(ies) (@dvnstrcklnd any issues with this choice of wording?)
• New button should be blue (like in sample types page)
• Disable save button when required fields are not filled or form has errors (enable when no errors), this is prevent the specified issue from occuring
• Drop down menus should be legible
• Handler (object category) should be dropdown with an option to create a new category, default will be "choose one"
• Cost per item should be limited to a valid dollar amount (only allow a single . as non numeric input, with only two decimal points following)