-
-
Notifications
You must be signed in to change notification settings - Fork 708
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
Adapt to core changes (addon.xml) #1872
Conversation
✅ Thanks for your pull request to the openHAB documentation! The result can be previewed at the URL below (this comment and the preview will be updated if you add more commits).
To edit notification comments on pull requests, go to your Netlify site settings. |
Can you check if something went wrong with the commits on your side? |
Looks like line-ending changes. According to https://github.com/openhab/openhab-docs/blob/main/.editorconfig CRLF is expected, what is exactly what I committed. Can you comment what is the correct line-ending (it seems it was LF before, according to my local git client). |
It is ok for me the change the line endings to crlf. Maybe it isn't used that often and we missed those files for a long time. But ofc those changes are a bit misleading to the original intention and pr title. |
I can revert that, not an issue. It wasn‘t even intentional, my IDE just picked up what the repo provided as suggestion. I believe in most other repos we use only LF. |
Then i should check this in egenral and adapt the config to the generic approach, where LF would be fine at all. In this case reverting would be good for th epr to just reflect the intentional changes. |
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.
Sorry, this went out of my focus for way too long.
I didn't realise, that you already fixed everything with the commits.
I have just one small finding, which i will solve myself.
Found needed changes after solving the merge conflicts.
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.
Again some small comments/questions, from checking the preview after solving the conflicts.
Please make sure that this is only merged after the core-PR has been merged, otherwise we'll have an inconsistent documentation. |
I have added the dependency label and subscribed to the core pr. :) |
@@ -142,7 +142,7 @@ module.exports = [ | |||
children: [ | |||
['developer/', 'Overview & Introduction'], | |||
'developer/guidelines', | |||
'developer/bindings/', |
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.
I would definitely suggest to keep the "bindings" menu in place, just as we have dedicated entries for other add-on types like automation addons, transformation services, voice add-ons etc.
What would imho make sense here is to add a new menu entry for everything that generally applies to all add-ons and this new page could then link to the different specific add-on pages as well.
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.
The problem is that we don't have content for that page. Duplicating what is written on the general page makes no sense.
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.
Well, a few parts could be moved from the binding page to the add-on page, like the description about the addon.xml, the info on how to add a logo for the add-on and similar.
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.
After I did that, there was no content left :-)
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.
Hm, I see your point, but I am a bit puzzled, because on https://www.openhab.org/docs/developer/bindings/ I see a lot more content about how to develop a binding. You seem to have moved all the files that contribute to this page to /developer/addon
.
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.
Sometimes I'm a bit slow... Is this version better?
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.
Yes, thanks - that look better!
6465800
to
5b2e346
Compare
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.
Do you have any idea, why Github does not properly show the changes that you made, but rather shows the full files to be changed (e.g. developers/bindings/index.md)?
This makes reviewing hard, but I just trust that there were no irrelevant changes.
developers/addons/index.md
Outdated
title: Add-ons | ||
--- | ||
|
||
# Developing an add-on |
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.
# Developing an add-on | |
# Developing an Add-on |
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.
Yes, that's due to an incorrect .editorconfig
in this repo (it defines CRLF instead of LF which is actually used).
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.
This should be fine now.
@@ -142,7 +142,7 @@ module.exports = [ | |||
children: [ | |||
['developer/', 'Overview & Introduction'], | |||
'developer/guidelines', | |||
'developer/bindings/', |
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.
Yes, thanks - that look better!
Signed-off-by: Jan N. Klug <[email protected]>
Signed-off-by: Jan N. Klug <[email protected]>
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.
Wonderful - that's how it should look like! 👍
Some documentation files were moved in openhab#1872 which caused these links to be broken. Signed-off-by: Wouter Born <[email protected]>
Some documentation files were moved in #1872 which caused these links to be broken. Signed-off-by: Wouter Born <[email protected]>
Some documentation files were moved in #1872 which caused these links to be broken. Signed-off-by: Wouter Born <[email protected]>
Some documentation files were moved in #1872 which caused these links to be broken. Signed-off-by: Wouter Born <[email protected]> Co-authored-by: Wouter Born <[email protected]>
Depends on openhab/openhab-core#3050
Signed-off-by: Jan N. Klug [email protected]