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

User lists now working properly with datalist. Fixup for many areas where error constructor was being called with object instead of string

Browse Source
This commit is contained in:
John Cardinal
2020-12-08 20:25:55 +00:00
parent 0b7f418c11
commit 9f0ef1a8f5
19 changed files with 68 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
ayanova/devdocs/todo.txt
View File

@@ -5,28 +5,6 @@
MISC ITEMS THAT CAME UP
todo: customer users and regular users really need to reconsider not using a standard grid,
seeded huge basically dies waiting
However, how real is that scenario in the first place?
Ideally though for many reasons it should be a regular datagrid
Look into it, find out why it isn't and can it be implemented?
Also roles could then show on the customer-user grid which would be handy for some
AT LEAST put a wait spinner on that page
ACTIONS:
XMake a snapshot commit at both ends tagged with the fact about to do mucho fuckery and may need to revert
XMake copies of gz-data-table.js and inv-parts.vue
Xmake a InsideUserDataList.cs at server
XModify inv-parts.vue to show the insideuserdatalist in a gz-data-table
Xwork on gz-data-table and attempt to have roles work, use the code in adm-users rolesDisplayFromRoles method
FieldDataType=17 for roles
XSee if can get it to work adequately without worrying about filtering on roles
XNOPE, doesn't offer to filter, only sort and I'm happy with it for now.If it basically is working well enough regardless of filtering roles then see if its even conceivable that server could filter roles
maybe the client sends a lot of or i.e. roles = (64 or 1234 or 32768) however that shit has to work
if conceivable then need to make a copy of the ay-data-list-view.vue and modify to work with roles as a filter
XMake sure can print, bulk ops etc
If all is well then move it into the regular adm-users and replicate to cust-users and ditch the shitty current half-ass grid
Remove the routes that were being used for inside and outside user lists as they are no longer reqd.
$profit
todo: throw new Error() code *MUST* put only a string into the constructor of error. Putting a object is wrong and will result in errors that say "Error: [object Object]"
Search for all instances of throw new Error and ensure it's a string not an object, use stringify if necessary when all else fails