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
2020-11-26 15:57:10 +00:00
parent 2f8b4e25e4
commit ae4adc8d45
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
ayanova/devdocs/todo.txt
View File

@@ -35,6 +35,14 @@ To REMOVE: apt-get remove dotnet-runtime-3.0 (replace 3.0 with whatever version
MISC ITEMS THAT CAME UP MISC ITEMS THAT CAME UP
todo: import items triggers notification checks since they are going through the regular create process
e.g. this throws up all the time during v8 migrate: throw new System.NotImplementedException("Awaiting workorder object completion");
I'm thinking there needs to be a skip notification check for import objects somehow, but how and where to set that
maybe a non persisted field for skip_notify_check or something on objects?
Need to consider normal usage vs import etc
also import export code, should it trigger notification?
If a user imports a bunch of clients from a json file and they happen to have a notification set for create client then could get thousands of notifications
todo: network error should not show on NEW COUNT for notifications because it's looping over and over and keeps showing that error todo: network error should not show on NEW COUNT for notifications because it's looping over and over and keeps showing that error
That particular code should just show the error once maybe then go about it's business quietly? That particular code should just show the error once maybe then go about it's business quietly?
or maybe it's kosher as is, a dev environment is not the same as production after all or maybe it's kosher as is, a dev environment is not the same as production after all