For those who want to ask for debugging help here or just want more consistent flows in general from Switch users in your shop, Dwight and I have started a style guideline document. This document has some best practices that we feel improve readability and will assist in troubleshooting if followed.
It's a working document, so many changes to come. Anyone can suggest changes, so please do so if you have ideas or disagree with a guidelines.
Find it here: https://github.com/open-automation/swit ... guidelines
Switch Style Guidelines
Switch Style Guidelines
Last edited by gabrielp on Wed Jun 22, 2016 6:19 pm, edited 1 time in total.
Chat: open-automation @ gitter
Code: open-automation & dominickp @ GitHub
Tools: Switch, Pitstop, EPMS, Veracore, PageDNA, SmartStream, Metrix
Code: open-automation & dominickp @ GitHub
Tools: Switch, Pitstop, EPMS, Veracore, PageDNA, SmartStream, Metrix
Re: Switch Style Guidelines
A good idea. Have thought of this when my flows has grown and become more and more complex. Will try to use it in the future!
Between jobs!
Re: Switch Style Guidelines
I also enjoy the effort. It's always great and enlightning to confront its own habits to other experienced fellows practices!
Re: Switch Style Guidelines
Revised and moved to Github: https://github.com/open-automation/swit ... guidelines
Chat: open-automation @ gitter
Code: open-automation & dominickp @ GitHub
Tools: Switch, Pitstop, EPMS, Veracore, PageDNA, SmartStream, Metrix
Code: open-automation & dominickp @ GitHub
Tools: Switch, Pitstop, EPMS, Veracore, PageDNA, SmartStream, Metrix