search

raisely / cli

Raisely CLI for local development
Other
8 stars 6 forks source link

Add current campaign message to warning #31

Closed danalexilewis closed 2 years ago

danalexilewis commented 2 years ago

I am aware that custom components are deployed org wide, so this is less important for components.

However for deploying scss it would be good if the warning also told you which campaign you are overiting.

Obviously it matters less if you have disabled the ability for users to edit files through the ui, but as we are transitioning our client from ui edits to source controlled edits, thats not the case for us.

image

tommaitland commented 2 years ago

Currently raisely deploy deploys all of the campaigns in your .raisely.json file (see reply to https://github.com/raisely/cli/issues/34). We could still list them out here though, would happily accept a PR on this.

danalexilewis commented 2 years ago

@tommaitland i followed the QuickStart guide and I don’t remember it telling me to edit the campaigns in the .raisely.json file.

if I add the uuid for the staging and production environments, will this mean it deploys to both every time?

Regarding the message, I think what throws me is that you can still deploy to a campaign even if the campaign array is empty in the .raisely.json file.

Hmm, if that is the file where config goes - tbh I’d expect it to error out of its empty.