This commit is contained in:
@@ -14,11 +14,20 @@ TODO CLIENT STUFF
|
||||
|
||||
TODO NEXT
|
||||
|
||||
### THERE!
|
||||
See server project widget validation code which will now give server errors on certain values so can proceed with work.
|
||||
Current issue is where to put notifications, code is to help test also as I'm not sure if server errors will be preventing submit when their are no field errors etc
|
||||
|
||||
Issues:
|
||||
|
||||
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: need to display multiple types of messages, best way to do that??
|
||||
- DONE: Local validation errors - this works and is done
|
||||
- DONE: Server errors - This works and is done
|
||||
- Important transient application messages, equivalent of dialog boxes that popup in apps, i.e. "This object has broken rules, fix them to be able to save" or "Insufficient rights" or whatever
|
||||
- Dialogs suck in web ui, so this should be right on the page itself in an alert probably
|
||||
- Notifications, stuff that you want to know is there and can go and look at but isn't urgent enough to put in the users face
|
||||
- Used for notification system, non-urgent system messages, direct messages from users etc, anything that isn't immediately important
|
||||
- This seems like an application wide thing so maybe a bell icon that takes to another area of the program, or opens a div at the top or bottom of the page??
|
||||
|
||||
|
||||
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
|
||||
|
||||
@@ -214,6 +214,8 @@ export default {
|
||||
// .catch(function(error) {
|
||||
// });
|
||||
} else {
|
||||
//say something so the user knows there is an issue
|
||||
alert("STUB: You can't do that, there are broken rules");
|
||||
}
|
||||
} //end of submit()
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user