"coast-dev" vs "coast" with mode toggle

[GregPeden]

I'd like to raise one issue with using a special "coast-dev" command for development, and that during practical testing on projects wired up to call "coast", they cannot be used to practically test development changes without making changes to skill / agent docs.

I would propose instead a means of changing whether "coast" invokes the local "latest" official installation vs the local development version. Right now I am experimenting with a command which toggles if coast points at the dev server or the "installed" build. This allows my project I am using to test practically to use the dev build without any tooling changes.

Thoughts?

[jamiesunderland]

I'm all for it. I hate this setup but what I've been doing is sticking to coast-dev for local changes, I then test with coast for testing the updates.

I'm running into this very issue right now actually. It's a nightmare for what I'm doing, so if you want to take a crack at the DX for this I would love nothing more in the world.

I would propose instead a means of changing whether "coast" invokes the local "latest" official installation vs the local development version. Right now I am experimenting with a command which toggles if coast points at the dev server or the "installed" build. This allows my project I am using to test practically to use the dev build without any tooling changes.

@GregPeden you have my blessing. If you can update the README.md with whatever you come up with I'll incorporate it.

[GregPeden]

I found out my bashrc solution to create a switcher for "coast" doesn't work in the VS Code IDE so I'm trying to understand that better.

[jamiesunderland]

All good. Just let me know what you want to do. If it's sane, I'm happy to add it.

[GregPeden]

I have had success with just always telling the agent "use command 'coast-dev' in place of 'coast'" and it's good at obliging that.