Versioning scripts & Builds
Posted: Tue Feb 02, 2021 12:25 am
I understand the concept of script folders vs built/packaged .sscript files.
What I don't get is the development process they want people to follow. Let's say I have a project that holds all of the script folders that I use in a project. This is fairly large 200+ scripts.
1. Each has its own development folder.
2. When developing you point to the .sscript file in the folder.
3. when done you build it and tell the flow to look at the newly built script? This seems clunky to have to go back and repoint the script in the flow to the newest built script.
* Do you build it in the same as the script folder? Then you don't have to update where it's pointed? seems like an anti-pattern.
4. how do you go about automating this and removing human error?
What I don't get is the development process they want people to follow. Let's say I have a project that holds all of the script folders that I use in a project. This is fairly large 200+ scripts.
1. Each has its own development folder.
2. When developing you point to the .sscript file in the folder.
3. when done you build it and tell the flow to look at the newly built script? This seems clunky to have to go back and repoint the script in the flow to the newest built script.
* Do you build it in the same as the script folder? Then you don't have to update where it's pointed? seems like an anti-pattern.
4. how do you go about automating this and removing human error?