This commit is contained in:
@@ -44,10 +44,22 @@ CURRENT ROADMAP
|
||||
|
||||
CURRENT TODOs
|
||||
=-=-=-=-=-=-=
|
||||
|
||||
Happy monday!!
|
||||
In the midst of custom form saving which also requires a little modification in the server see FormCustomBiz GetAsync for details
|
||||
then back here to code out the PUT route save of the form and also update local store.
|
||||
|
||||
TODO: Form customization
|
||||
|
||||
- When go to save then synthesize the record to send back
|
||||
- Update the Store on success
|
||||
- Do not add any custom fields not set to be displayed, their mere presence in teh template means they are to be displayed
|
||||
- SAVE
|
||||
- Update the Store on success
|
||||
- Do not add any custom fields not set to be displayed, their mere presence in teh template means they are to be displayed
|
||||
- POST vs PUT? Is post ever appropriate? Shouldn't every form have a custom if it can already and if it's fetched and doesn't exist make one?
|
||||
- Maybe need to modify the db init code in server to also create formCustom for every possible formCustom object and then only have a PUT route, no post?
|
||||
- Perhaps GET route will create one automatically if it's something that should exist but doesn't and return that? Dynamically?
|
||||
- Saves data storage for unused forms, but really that won't be shit anyway so...?
|
||||
|
||||
|
||||
TODO: HELP LINKS
|
||||
- Make sure each form has a unique help link and also make a stub page in the documentation for that help link to be filled in later or now if applicable
|
||||
|
||||
Reference in New Issue
Block a user