-
-
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
[Sitemaps] Charts: Documentation for legend parameter #518
[Sitemaps] Charts: Documentation for legend parameter #518
Conversation
Signed-off-by: Holger Reichert <[email protected]>
Hello @hreichert, |
No, he shouldn't! |
OK, so this is ready for merge? |
I would say so - @ThomDietrich do you agree on the versioning topic? |
Hey @kaikreuzer,
When writing the above comment I thought (3) is a good middle path without any drawbacks. But I don't want to overcomplicated it (all binding docs have the same issue, hence this is just a drop in the ocean) and rather finish the versioning feature in the next 2-3 weeks. Not sure if I can implement it before the Smart Home Day, otherwise we can discuss details there. Small Side Note: I don't want to stress this too much but I feel like I should at least mention it: It happens that I do not react to messages including exclamation marks... No hard feelings, best wishes, Thomas ;) |
@hreichert, I didn't say it before but thanks for your contribution! Looking forward to your next improvement idea ;) |
Imho the drawback is that we won't easily find all the places where we "temporarily allowed" that - and specifically, it encourages others to do it the same way and that's what we should avoid as it defies the versioning approach.
You mean the small single one from me above? Then never mind, because it was not targeted at you at all - its only purpose was to get @hreichert's attention in time before he puts efforts into changing the PR in a way that we eventually do not want. So I hope this use of an exclamation mark finds your acceptance ;-) |
No problem. Messages can easily misinterpreted and I think everything is settled. Let's continue over in #520 ! |
I spent 20 minutes figuring out why legend did not work on 2.0 :) |
@skatun ouch :) Two questions though: Why are you not using 2.1 and Do you know that by now we actually have a versioning system on the documentation page? |
Why are you not using 2.1 : Because you said not to upgrade because of some error in the old version: So I am waiting for the DMX to be implemented before I start a fresh start, is the GPIO also fixed now?(So that we do not run as root anymore) I am renting out one room, so I can not afford the system to go down on upgrade! |
This is an old comment and 100% directed at openHABian, not openHAB 😃 Sorry for the DMX thing but you know that you can always add a Pull Request, right? I've btw just recently changed the openhabian structure, making everything easier to understand and use: openhab/openhabian#241 Remember: Additions and improvements to the openhabian-config menu can also be used by older installations. You just have to "Update" to receive the latest version. If you can't afford the downtime, how about a second RPi which you can exchange after everything is setup? Just an idea ;) If you have further questions, please contact me privately rather than in this Issue. Best! Thomas |
Regarding this ESH PR: eclipse-archived/smarthome#4291
Add documentation for the new
legend
parameter to theCharts
section of sitemap.mdSigned-off-by: Holger Reichert [email protected]