admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-10-22 19:32:09 +00:00
parent d6848d3e5d
commit ed5d499aa0
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
ayanova/devdocs/todo.txt
View File

@@ -247,6 +247,10 @@ function ayGroupByTag(reportDataArray, tagContains) {
- 1 todo: firefox schedule fix: https://github.com/vuetifyjs/vuetify/issues/14243#issuecomment-944907925 - 1 todo: firefox schedule fix: https://github.com/vuetifyjs/vuetify/issues/14243#issuecomment-944907925
- 1 todo: admin-history page showing http://localhost:8080/adm-history LT:Global but other things are properly translated - 1 todo: admin-history page showing http://localhost:8080/adm-history LT:Global but other things are properly translated
-1 todo: (SERVER / CLIENT) server metrics database tables "xx others" always shows at top, sb either at very bottom or removed entirely? It's confusing
actually, why is it showing so much data, shouldn't they be in the list if there is that much data in some of those tables?
or should literally all tables show maybe, that might be more useful, no cut-off?
- 1 double check roles at client, the way authorizationroles.hasrole is coded makes me think it might be wrong - 1 double check roles at client, the way authorizationroles.hasrole is coded makes me think it might be wrong
it only checks that the value is nonzero but in postgres I noticed it needs to compare if the resulting value equals the exact role being checked it only checks that the value is nonzero but in postgres I noticed it needs to compare if the resulting value equals the exact role being checked
i.e. it's not enough to go userroles & desiredrole>0 but rather userroles&desiredrole==desiredrole i.e. it's not enough to go userroles & desiredrole>0 but rather userroles&desiredrole==desiredrole
@@ -420,7 +424,8 @@ todo: 3 Schedule form reporting?
todo: 1 Test with expired key, can superuser login and no one else?? **CRITICAL** todo: 1 Test with expired key, can superuser login and no one else?? **CRITICAL**
todo: 1 erase database is way too fucking slow
it needs to work fast every time due to migrators testing etc
todo:1.5 Joyce case 3931 test restore of 4alarm data todo:1.5 Joyce case 3931 test restore of 4alarm data
actually, try it here first with small amount of data then try the huge one actually, try it here first with small amount of data then try the huge one