-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix state/props in all Tasks components #455
Comments
Remember to fix state and props in all corresponding menu bars, as well. |
I believe where
Right now, I really just want to get Field Kit Core's basic functionality down pat, so I know entities with basic attributes are being stored and synced properly. Details of the Tasks module itself, while vital for the beta release, are a little out of scope for the original goals I had for the alpha, which was really to make sure core and farmOS.js were working as expected. Perhaps there's a more elegant way, but I'm just going to comment out those sections of the template for now, so I can pick up easily when I get to those issues in the beta milestone. I'll open issues for quantities and movements once I'm done with this basic prop/state stuff, just in case I figure out an easier way before then. |
After I'm done with |
Once I've finished #454, I need to comb through the all the templates and scripts in these SFC's to fix references to properties on logs, assets, etc that have changed in 2.x. For example,
log.done === true
needs to be changed tolog.status === 'done'
.TasksAll.vue
TasksFilter.vue
(Refactor TasksFilter using new loadLogs action #398)TasksEdit.vue
(might skip; see Integrate farmOS-map 2.0 #458)TasksMap.vue
The text was updated successfully, but these errors were encountered: