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-05-06 22:03:46 +00:00
parent 7bbafb7cad
commit 15e6657472
1 changed files with 15 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
ayanova/devdocs/todo.txt
View File

@@ -72,8 +72,9 @@ CURRENT TODOs
CURRENT ITEM: CURRENT ITEM:
BIZ OBJECT STUBBING FOR EXPORT TESTING OF HUGE ATTACHMENTS AND WIKI AND ATTACHED DOCS BIZ OBJECT STUBBING FOR EXPORT TESTING OF HUGE ATTACHMENTS AND WIKI AND ATTACHED DOCS
TEST: Is my ef core relationship enough with just annotations and navigation properties or do I need to define shit further TEST: Proposed workorder structure and routes
- Test create, retrieve, cascade delete See below PROPOSAL section
TEST EXPORT BIG DATABASE WITH TONS OF ATTACHMENTS TEST EXPORT BIG DATABASE WITH TONS OF ATTACHMENTS
@@ -87,6 +88,12 @@ todo: PLANNING WORKORDER considerations:
QUESTIONS: QUESTIONS:
Why do I need to make a wo first before I can update it? (i.e. why did I make a CREATE route?) Why do I need to make a wo first before I can update it? (i.e. why did I make a CREATE route?)
BUSINESS RULES (v7)
In reality there are almost no business rules in v7 workorder graph.
Only serious one is woitempart requires serial if serialized
Rest are all related to length of fields, required fields, date order etc and only a few of those to boot
Looks like this is not an issue regarding v7 stuff at all
DEPENDENCIES DEPENDENCIES
Workorder is not dependent on it's children for anything Workorder is not dependent on it's children for anything
WoItem is not dependent on any of it's children WoItem is not dependent on any of it's children
@@ -119,10 +126,14 @@ todo: PLANNING WORKORDER considerations:
TEST TEST
Do a practical test of a mocked wo, woitem, woitemlabor or whatever, see how it would be updated, fetched concurrency checking etc Do a practical test of a mocked wo, woitem, woitemlabor or whatever, see how it would be updated, fetched concurrency checking etc
QUESTIONS: QUESTIONS:
How best to update, in bits and pieces? How to do CRUD efficiently with a workorder and client?
PROPOSAL: Send only changes in whole graph from client with an OP (for "operation") flag at each level indicating to change that part or not, a flag? PROPOSAL:
CREATE:
CreateFromxxxx routes (NO TEST REQUIRED)
POST accepts workorder full graph (test)
UPDATE: Send only changes in whole graph from client with an OP (for "operation") flag at each level indicating to change that part or not, a flag?
WO (OP flag=no change, no concurrency token, basically empty but for the fields that hold the descendents that are changed) WO (OP flag=no change, no concurrency token, basically empty but for the fields that hold the descendents that are changed)
woitem 0 (OP flag="Delete" and concurrency token, no other data with it, just the id and flag and ctoken) woitem 0 (OP flag="Delete" and concurrency token, no other data with it, just the id and flag and ctoken)
woitem 1 (OP flag ="update", all fields as in a "put" operation, nothing left out, assumed all are changed) woitem 1 (OP flag ="update", all fields as in a "put" operation, nothing left out, assumed all are changed)