You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rendering the door/lock configuration is currently going to be a little painful if we ever change our door configurations on the VEM150 line. This isn't likely to spring up un-announced, however I did want to flag that we'd like to use a shorter-form to specify the configuration, and render a door configuration based on a simple map.
The text was updated successfully, but these errors were encountered:
would we want a similar issue opened for the i2c plugin (which exposes the lock devices) so we could also use that shorter-form to render lock configs?
The i2c chart has the template generation pattern, I'm not sure if we want to move it further down the dependency tree into the app, or a sidecar script, but yeah, feels like there's opportunity for these tasks to be linked and a uniform generator/template pattern emerge.
I think realistically moving it down somewhere would be nice, since the readability/maintainability of that template generation is uhh.. tribal knowledge and a headache at best.
I don't fully know if it could be pushed down to the plugin level, but it certainly could be put into some init/sidecar script. Possibly adding in support for some config template rendering stuff into the SDK would be a good idea, since if we are using it for one plugin, its entirely possible it would be useful for others, so getting generalized baked-in capabilities for that feels useful.
Rendering the door/lock configuration is currently going to be a little painful if we ever change our door configurations on the VEM150 line. This isn't likely to spring up un-announced, however I did want to flag that we'd like to use a shorter-form to specify the configuration, and render a door configuration based on a simple map.
The text was updated successfully, but these errors were encountered: