You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Related to lazy-loading: once the lazyLoadTasks method is merged, if you have a very large directory full of local tasks, it can be a pain to manually maintain this list. For one project I built a grunt task that you can run on a directory and spit out the JSON data that becomes your task's lazy-load config (a map of file names and task names, basically).
I'm not sure exactly how you'd structure it, but it would be kind of cool if we could get this tool into this package proper, and then a user that's already using it would get it "for free".
(The user can then copy/paste this updated def into their Gruntfile, or, they could get fancy and hook this into git-precommit and run it any time a task is added, etc.)
The text was updated successfully, but these errors were encountered:
Related to lazy-loading: once the
lazyLoadTasks
method is merged, if you have a very large directory full of local tasks, it can be a pain to manually maintain this list. For one project I built a grunt task that you can run on a directory and spit out the JSON data that becomes your task's lazy-load config (a map of file names and task names, basically).I'm not sure exactly how you'd structure it, but it would be kind of cool if we could get this tool into this package proper, and then a user that's already using it would get it "for free".
(The user can then copy/paste this updated def into their Gruntfile, or, they could get fancy and hook this into git-precommit and run it any time a task is added, etc.)
The text was updated successfully, but these errors were encountered: