Bugzilla – Full Text Bug Listing
| Summary: | It should be possible to apply the default rules as a fallback even if some rules exist for some elements | ||
|---|---|---|---|
| Product: | [Modeling] Sirius | Reporter: | Pierre-Charles David <pierre-charles.david> |
| Component: | Properties | Assignee: | Melanie Bats <melanie.bats> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | info, stephane.begaudeau, steve.monnier |
| Version: | unspecified | Keywords: | triaged |
| Target Milestone: | 4.1.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | https://tuleap.eclipse.org/plugins/tracker/?aid=505 | ||
| See Also: |
https://git.eclipse.org/r/82362 https://git.eclipse.org/c/sirius/org.eclipse.sirius.git/commit/?id=28884344a71a0e35f90f91d970519d1e06e8e522 https://git.eclipse.org/r/82700 https://git.eclipse.org/c/sirius/org.eclipse.sirius.git/commit/?id=365a2626341a806c2388e825e3b15bfd450317af |
||
| Whiteboard: | |||
For 4.1, we'll simply add an action in the VSM editor to inline a copy of the default rules. The specifier can then tweak them to only be used for elements for which he does provide other, more specific, page definitions. We'll have to take care of not using any internal-only mechanism in the default rules, as this means they will be exposed to specifiers. New Gerrit change created: https://git.eclipse.org/r/82362 Gerrit change https://git.eclipse.org/r/82362 was merged to [master]. Commit: http://git.eclipse.org/c/sirius/org.eclipse.sirius.git/commit/?id=28884344a71a0e35f90f91d970519d1e06e8e522 This is done except for missing documentation. New Gerrit change created: https://git.eclipse.org/r/82700 Gerrit change https://git.eclipse.org/r/82700 was merged to [master]. Commit: http://git.eclipse.org/c/sirius/org.eclipse.sirius.git/commit/?id=365a2626341a806c2388e825e3b15bfd450317af Fixed. FIWI, I've reworked the previous solution to avoid highjacking the very first menu. It doesn't look like a MenuBuilder-based approach would have allowed that (or at least given the time available I wasn't able to find how). Available in Sirius 4.1.0, see https://wiki.eclipse.org/Sirius/4.1.0 for details. |
Currently, as soon as we define even a single user rule in the VSM, which may only apply to elements of type T, the default rules are completely disabled for all types, including the ones we did not define any rule for ("all or nothing" effect). We the specifier defnes a Property View Description, he should be able to indicate whether these rules apply instead of (current behavior) or in addition to the default rules.