Some possible UI fixes for RWMMAs ( records with many many associations ) and tree reordering.
This is a first pass, there are bugs, tests are coming, and many of these elements still need to be refined.
Branch includes the following changes:
Form UI changes:
- Record sections with over 5 subrecords will not load initally, but display a block that says "Click To Load Records". Users can click these records to have the JS handle the DOM elements.
- Record edit forms will only call the record once on the initial load. ( currently, JS fires requests to the backend twice ).
- Edits in the form makes the tree read-only until the form is saves or reverted.
Tree UI changes:
- Move requests to the backend will cause the tree to be locked until the backend response has completed.
- Move requests will lock the record form and require the user to reload the record form section ( note: note the entire page!)
- Completed move requests will refresh the targeted section with new data from the backend.
- The new refreshed data will be checked with the intented ordering that was submitted. If there is a difference in the intended order vs the actual order ( i.e. order as presented in the UI tree vs. order called from the database), the user will be alerted and the form will submitted the entire series to be reordered by the backend.