This commit is contained in:
2019-04-03 00:04:44 +00:00
parent e4837d44a4
commit c4a495bb9a
3 changed files with 67 additions and 14 deletions

View File

@@ -14,12 +14,63 @@ TODO CLIENT STUFF
TODO NEXT
Make the stuff happen to resolve the first open issue below
Issues:
won't show multiple lines in v-alert from my code but will if static element with <br/> at end of each line
Not sure this is the correct approach, it's needing to iterate the return error object multiple times which is a code smell
PENDING FIXED ISSUE: won't show multiple lines in v-alert from my code but will if static element with <br/> at end of each line
ISSUE: Not sure this is the correct approach, it's needing to iterate the return error object multiple times which is a code smell
- Once to see if there are errors and another time to build up the errors
- Maybe it should be called once only as a method after the server returns the results and the gzvalidate populates a key on the data object in the form which in turn drives the error box?
FIX:
Need to test with full features, so plow ahead getting to a normal cycle of errors and then go back and fix the things that don't work later
Scenarios:
- DONE: Local form validation errors display correctly and are cleared when edited
- Server form validation errors displayed correctly
- control ones under control where local form validation errors show
- whole object ones at top
- Server form validation errors cleared in individual inputs upon any change to them (but form overall ones stay until submitted)
- On submit:
- Doesn't happen if any local validation errors
- All server errors clear on submit
- Validation short circuits if form is loading and no data yet
- Validation short circuits if no server errors at all
DIRTY CHECKING to short circuit rule checks
direct control properties when control was changed / is dirty:
=-=-=-=-
hasColor: true
hasFocused: undefined
hasInput: true
hasMouseDown: undefined
initialValue: 8212
internalChange: true
isClearing: undefined
isFocused: true
isResetting: undefined
lazySelection: undefined
lazyValue: "82121"
Same properties when control was NOT changed:
=-=-=-
hasColor: undefined
hasFocused: undefined
hasInput: true
hasMouseDown: undefined
initialValue: null
internalChange: undefined
isClearing: undefined
isFocused: undefined
isResetting: undefined
lazySelection: undefined
lazyValue: undefined
LOADING CHECKING to short circuit rule checks when form is first loading
Vuetify Inputs have a loading property, can that be used to super short circuit rule checking?