This commit is contained in:
2021-04-01 01:02:05 +00:00
parent 4b6fd0a7b3
commit 3eda559df9
2 changed files with 7 additions and 7 deletions

View File

@@ -37,7 +37,9 @@ namespace AyaNova.Api.Controllers
serverState = apiServerState;
}
//todo: finish this off, it's missing some shit, and also check it's modernized
//will also likely need a seperate fetch route for just the header and just an item
//prefer named routes for each rather than some kind of parameter for existing routes, i.e. get{id} for whole graph and get headeronly/{id}
/*
██╗ ██╗ ██████╗ ██████╗ ██╗ ██╗ ██████╗ ██████╗ ██████╗ ███████╗██████╗

View File

@@ -17,16 +17,14 @@ namespace AyaNova.Biz
Fetch must be able to get entire graph or from any level down or single header only as required
probably need a woheaderfetch route separately
TODO: currently need to go top to bottom and pick through and modernize code, make sure all descendants are coded for, then routes, then come up with a way to test my UI theory as simply as possible
Keeping in mind that too much time invested at this end might be a mistake because client should drive the backend choices
So I guess get a minimally working backend, then a minimally working front end to just get a gist of what the path forward is and then can jump in with real world shit
I guess just implementing a very simple portion like from wo down to item down to a single grandchild makes the most sense
TODO: Routes then front end stuff can start and may god have mercy on my soul! ;)
todo: Don't all *child items require a transaction to be passed for *any* crud op, i.e. including put and etc?
As they might be called from a parent transaction?
(wait until front end to decide this and do some testing etc grok it out)
todo: search for singleordefaultasync to find any missed *GetAsync items using old direct fetch
*/