[Question] Best practice around "remote" taskfiles
As part of Wails v3, we're introducing "Services" which are a little like plugins, but provide additional features. These will be published as Go modules. In certain scenarios, it would be great to also distribute a Taskfile to add functionality to the main build system. I'm aware people can opt into Remote Taskfiles and then access the Taskfile via a URL, but there's a few concerns:
1. Keeping it in sync with any module updates
2. Being transparent about what is being run
3. Allowing them to customise the task
Is the best thing to do just to download the remote module to a local location (like go vendor) and just get people to include the local taskfile?
1 Reply
Hi @leaanthony. Sorry for the wait, it was a holiday here in Brazil in the past days, so I was OOO.
I don't have the full context of what you're trying to do at Wails, but from what I could understand, I'd say it'd be better to disallow remote Taskfiles or vendor them somehow so we avoid issues with synchronization. If the plugin version differs from remote, you could have issues.