This commit is contained in:
@@ -41,11 +41,27 @@ All platforms and browsers
|
||||
- DONE Make about contextual and insert a menu item to view log
|
||||
- DONE WIRE up save menu item and add code to disable save on broken rules (and make red, disabled etc)
|
||||
- DONE Move wire up event code from app.vue to gzmenu and call it from app.vue
|
||||
### - Need rights in form state so can easily enable / disable etc
|
||||
- BIG TODO: it would be far nicer if rights to objects were stored in a single JSON fragment that could be easily copied into javascript and c#
|
||||
- code automatically builds rights collection from json fragment so can use it between both projects and more easily update it in one central spot
|
||||
- Get that working then come back to the rest of the rights in client side
|
||||
- Need to create sample users in server project that have all the different widget right combinations for testing purposes
|
||||
### - RIGHTS in form state so can easily enable / disable etc
|
||||
- Form (AND THE LIST OBJECT) should check rights and adapt accordingly
|
||||
- ReadFULL record but no change should show record read only
|
||||
- Delete should be checked
|
||||
- CHANGE should be checked
|
||||
- If no rights then should redirect back to HOME
|
||||
- If user attempts to load widget form but has no rights to widget server returns the NO rights code but that is triggering back to login
|
||||
- Should it do this? Normally would not be an issue because it wouldn't open that form unless they saved or manually typed a link to it
|
||||
- Technically it's incorrect, they don't have to login, they just can't get that record
|
||||
- Have a look at why it's redirecting and decide if this is worth a change
|
||||
- DONE BIG TODO: it would be far nicer if rights to objects were stored in a single JSON fragment that could be easily copied into javascript and c#
|
||||
- DONE code automatically builds rights collection from json fragment so can use it between both projects and more easily update it in one central spot
|
||||
- DONE Get that working then come back to the rest of the rights in client side
|
||||
- DONE ALREADY Need to create sample users in server project that have all the different widget right combinations for testing purposes
|
||||
- ??HOME not localized issue, on login, sometimes the home page is not showing as localized! Some kind of timing issue or wrong event used to localize it or something. ??
|
||||
- I see that HOME->BeforeCreate breakpoint is hit **BEFORE** the locale text has been fetched.
|
||||
- 1) this should never happen and is calling into question my use of promises here
|
||||
- 2) Make it happen that beforeCreate in home absolutely never gets called before all the init is done
|
||||
- 3) I think this means that login router push to HOME should not happen until init is done even earlier
|
||||
- So WTF on that, supposed to await the promise resolution from login then init and stuff, need to sort that, it's out of whack
|
||||
- Likely I'm not dealing with the promises properly
|
||||
- Wire up delete menu item
|
||||
- api code is stubbed out for delete, need to write that as well
|
||||
- DONE TODO navigating through menu doesn't "back" properly when clicking back on browser controls
|
||||
@@ -63,7 +79,7 @@ All platforms and browsers
|
||||
- DONE: Application name is all lowercase "ayanova" when installed to device, must be something in the manifest files?
|
||||
- Check about page localization code, is it firing in the right place because on Edge and iPad firefox it didn't show localized at first until a refresh so it fetched the keys but didn't display properly
|
||||
- Calendar on iPad in two occasions with ff and opera the calendar date could not be selected until a time was changed then the date worked. Before that it would always stay the same no matter what selection was made and the UI would not show a change on select or press of date either.
|
||||
- On login, sometimes the home page is not showing as localized! Some kind of timing issue or wrong event used to localize it or something. ??
|
||||
|
||||
- Navigation guard: navigate away with unsaved changes should warn and prevent but have option to continue anyway
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user