-
-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make functionSwitchConfig less cryptic in yaml file #4913
Labels
enhancement ✨
New feature or request
Comments
The common rule in this project is:
So, if this is changed, it will be a one-way street only. Otherwise the data model is too hard to maintain. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this feature request?
Is your feature request related to a problem?
currently parts of the yaml file are easy to understand and even update outside of the radio or companion. One area where they are decidedly complex and cryptic are the switches (like the six above the screen on a t-pro). There is a section titled
switchNames
which works well, but if you are trying to work out if the switches are 2POS or Toggle then you need to decrpt thefunctionSwitchConfig
integer which is not very intuitive.Describe the solution you'd like
perhaps ditch
switchNames
and replace it with aswitches
: array and each element in the array can have aname
and also atype
(and addstart
,group
andalwaysOn
I'm not sure how much version downgrading/backward compatibility you are aiming for in the yml files.
Describe alternatives you've considered
you could keep
switchNames
andfunctionSwitchConfig
and add in the switches section and update BOTH for a while so people can move back a version and then finally remove functionSwitchConfig in a later version.Additional context
No response
The text was updated successfully, but these errors were encountered: