This commit is contained in:
@@ -247,9 +247,6 @@ CURRENTLY DOING:
|
|||||||
|
|
||||||
|
|
||||||
OVERALL
|
OVERALL
|
||||||
|
|
||||||
- Decide on and implement "MARKED FOR DELETE" text that shows in sub items, it's just scaffolded in right now
|
|
||||||
perhaps a big red trashcan is adequate?? Although it doesn't really convey marked so much as being a control people will try to click on
|
|
||||||
- Test out role rights, login as various roles and ensure it works as expected
|
- Test out role rights, login as various roles and ensure it works as expected
|
||||||
- once past this step then second pass at new features **that affect models** (not necessarily UI stuff just fields required etc)
|
- once past this step then second pass at new features **that affect models** (not necessarily UI stuff just fields required etc)
|
||||||
Add items below that are just spurious and not tied to a particular case as v.next cases YAGNI/TTM!
|
Add items below that are just spurious and not tied to a particular case as v.next cases YAGNI/TTM!
|
||||||
@@ -258,7 +255,7 @@ OVERALL
|
|||||||
- load and stress test on client
|
- load and stress test on client
|
||||||
- ## Try to find every thing that will matter when more collections are added now, ensure a full flow from start to stop and everything in between to try to catch any gotchas now before get too deep into it ##
|
- ## Try to find every thing that will matter when more collections are added now, ensure a full flow from start to stop and everything in between to try to catch any gotchas now before get too deep into it ##
|
||||||
|
|
||||||
todo: deleted wo
|
|
||||||
todo: update on save??
|
todo: update on save??
|
||||||
can it fetch down changes or does that even make sense bandwidth wise
|
can it fetch down changes or does that even make sense bandwidth wise
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user