This commit is contained in:
@@ -44,17 +44,14 @@ CURRENT TODOs
|
||||
|
||||
@@@@@@@@@@@ ROADMAP STAGE 1 and 2:
|
||||
|
||||
|
||||
todo: custom fields currency type control NOT implement yet, are there others too?
|
||||
|
||||
todo: custom fields date only and time only are not setting but combined date/time is setting
|
||||
- It's possible I made a change in datetime that I need to also make in standalone separate ones to update properly
|
||||
- Maybe in event emitted?
|
||||
|
||||
todo: CUSTOMIZE not working on widget edit form
|
||||
todo: CUSTOM DATE FIELD NOT SETTING NOW??
|
||||
- Retest every kind of custom field
|
||||
todo: are *all* custom field types working? Not certain
|
||||
|
||||
todo: apparently I can change the buttons to display the text not uppercase with class="text-none" or something
|
||||
todo: apparently I can change the buttons to display the text not uppercase with class="text-none" or something, should I go back to buttons? (kinda looked cooler, but...)
|
||||
- https://github.com/vuetifyjs/vuetify/issues/3948
|
||||
|
||||
todo: save (post) of new record at client triggers renavigation to that page again which also triggers fetch
|
||||
- original:
|
||||
- So what's the point of returning the full record on post?
|
||||
@@ -62,6 +59,8 @@ todo: save (post) of new record at client triggers renavigation to that page aga
|
||||
- On the other hand, is the data still kept in the view or is create called again fresh and all that??
|
||||
- Actually, it really doesn't navigate if it can help it to refresh vue components
|
||||
- So, is it fetching a whole fresh record after save or using the results of save returned?
|
||||
- ANSWER: definitely fetching on save of new record.
|
||||
|
||||
todo: add refresh button above grid, reason being that we really don't want people refreshing the ENTIRE app with a full page refresh
|
||||
- Even though we support it, it's slow and could be an issue when running in application mode with no browser controls
|
||||
|
||||
@@ -92,10 +91,7 @@ todo: Created hook is probably where I should be doing the stuff I'm doing in be
|
||||
- Reason being that the data object is not fully set up in beforecreate but I'm putting data into it as if it is which seems weird
|
||||
- todo: perhaps beforeCreate is being used wrongly in widget edit form, need to take a re-look to ensure it's correct before I copy it endlessly
|
||||
|
||||
todo: CUSTOMIZE not working on widget edit form
|
||||
|
||||
todo: CUSTOM DATE FIELD NOT SETTING NOW??
|
||||
- Retest every kind of custom field
|
||||
|
||||
todo: toolbar above grid for filters, refresh etc (make it a standard component?)
|
||||
|
||||
|
||||
@@ -505,6 +505,7 @@ export default {
|
||||
//NOTE: will not cause a new navigate, almost nothing does unless forced with a KEY property or using router.GO()
|
||||
//but will trigger navigation guard beforeRouteUpdate which we use here in this form
|
||||
//to fetch data again
|
||||
debugger;
|
||||
vm.$router.replace(
|
||||
vm.$route.fullPath.slice(0, -1) + res.data.id
|
||||
);
|
||||
|
||||
Reference in New Issue
Block a user