-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[modbus][sunspec] Removed colons in Headline #7423
[modbus][sunspec] Removed colons in Headline #7423
Conversation
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks - I indeed wondered why the website build fails!
Will have a closer look at this bundle as well as it is not a binding, but a sub part of one. Seems that it already caused the release notes to go wrong...
@kaikreuzer could it be related to the feature? For mqtt and bluetooth (where we have subbundles, too) we have an aggregated feature which installs all bundles at once. IIRC the feature is used for something during the build, right? We decided against this aggregated feature here, but this could be changed (IMO the aggregated Features should be removed, I don‘t see why I have to install the homeassistant bundle if I don‘t use it, but want to use the generic MQTT channels). |
The features define the installable units - we have one feature per add-on. |
I can bring the feature in-line with the other ones tomorrow. But I still think this should be discussed for OH3. Especially for Bluetooth, where there are a lot of different bundles which probably will not be used all at the same time, the „always install everything“ strategy feels wrong. |
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch> Signed-off-by: Eugen Freiter <freiter@gmx.de>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch> Signed-off-by: CSchlipp <christian@schlipp.de>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch> Signed-off-by: Daan Meijer <daan@studioseptember.nl>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way. Signed-off-by: Jerome Luckenbach <github@luckenba.ch>
Those seem to make the website build fail, since the yaml frontmatter is parsed wrong this way.
cc: @kaikreuzer