I have developed a feature, npm dev run, copy the url to a new build, publish it, and it works right… , but every time i need to change the code, i have to create a new version of the app, then a new publish it, just for testing?? I feel this is not correct.
I should not have to make an app “live” just to be able to test it right?
I figured this by, going to installed apps in your Monday instance, finding your app and selecting view, then selecting use to apply it to your board (again). Doing this again will add the new integration. If your integration has structurally changed you’ll see the old one and now the new draft on your board automation, so, delete the old one and reconfigure the new one.
Now that I know how it works, it’s fine but feedback is that this is a less than ideal way to test new draft versions.
I still understand that you have to publish your first draft love to your account before you can start testing the first time round, and then continue to use drafts after that. This is another starting development quirk one has to get used to.
In all, thanks for the product I’m loving it and using it!