I've included a passed example demonstrating the inheritance of properties from a superclass role, as it was absent.
I've included a failed example showcasing a prohibited global property to underscore the significance of the edit mentioned in the first bullet point.
I've included an interesting example (both passing and failing) of the separator role, illustrating that it supports a specific property when focusable but not when static.
Need for Call for Review:
This will require a 2 weeks Call for Review
Pull Request Etiquette
When creating PR:
[ ] Make sure you're requesting to pull a branch (right side) to the develop branch (left side).
[ ] Make sure you do not remove the "How to Review and Approve" section in your pull request description
After creating PR:
[ ] Add yourself (and co-authors) as "Assignees" for PR.
[ ] Add label to indicate if it's a Rule, Definition or Chore.
[ ] Optionally request feedback from anyone in particular by assigning them as "Reviewers".
When merging a PR:
[ ] Close any issue that the PR resolves. This will happen automatically upon merging if the PR was correctly linked to the issue, e.g. by referencing the issue at the top of this comment.
How to Review And Approve
Go to the “Files changed” tab
Here you will have the option to leave comments on different lines.
Once the review is completed, find the “Review changes” button in the top right, select “Approve” (if you are really confident in the rule) or "Request changes" and click “Submit review”.
Make sure to also review the proposed Call for Review period. In case of disagreement, the longer period wins.
Closes: #2191
Updates:
Need for Call for Review: This will require a 2 weeks Call for Review
Pull Request Etiquette
When creating PR:
develop
branch (left side).After creating PR:
Rule
,Definition
orChore
.When merging a PR:
How to Review And Approve