README and rules.js: reword documentation#491
Closed
dilyanpalauzov wants to merge 1 commit intoopenhab:mainfrom
Closed
README and rules.js: reword documentation#491dilyanpalauzov wants to merge 1 commit intoopenhab:mainfrom
dilyanpalauzov wants to merge 1 commit intoopenhab:mainfrom
Conversation
florian-h05
reviewed
Oct 15, 2025
Contributor
florian-h05
left a comment
florian-h05
left a comment
There was a problem hiding this comment.
Why UI based and not UI-based?
I am not sure what is the better term …
Contributor
Author
|
I have no preference for UI based or UI-based, you can consult others. Currently it is sometimes written so and sometimes the other way. |
Contributor
|
After all, if won’t matter that much I think. Those terminologies very likely will soon be replaced by a technically more correct terminology. |
Contributor
|
Superseded by #492 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make consistent no-hyphen policy for the terms “UI based” and “File based” rules and scripts.
Spell explicitly that parallel execution is blocked only when many rules originate from the same .js file.
Use on more places “separate dedicated” together for context, otherwise the question arises what is a separate context, which is not a dedicated context. I do not know if there should be a comma between separate and dedicated, but whether there is a comma should be consistent.