jgaehring
commented
2 years ago At this point I'm going to operate on the assumption that I will make Tasks a field module, and we can make a final decision just prior to beta release (hence I'll be leaving this open for now).
It may even be instructive to separate Tasks into its own repository, or at least give it a separate development environment and build process, in preparation for creating a template repo (#422). It will also aid in the migration to Vue 3 (#420), since the biggest breaking changes from 2 to 3 will primarily effect how field modules are mounted (ie, how their components are registered to the main application instance and added to the router). Developing with a module that's as close to the real thing should provide better feedback on what works and what doesn't.
I think it's worth revisiting this, since we're starting fresh, in a sense, with 2.x of both farmOS and Field Kit.
I guess I'd really like to see the Tasks module become a true Field Module, so users can disable it if they choose (they can't if it remains a build-time component), but include it as a default module in farmOS itself, so it still works "out of the box".
A related issue, which I may open separately, is whether the Tasks module should work prior to login. I'm already in favor of disabling all functionality while logged out, and this seems like another good reason to drop it.