| Summary: | A theme contribution for one application affects the other | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ivan Furnadjiev <ivan> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | 1.5 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Ivan Furnadjiev
I don't see the problem. Controls demo and examples demo are two entrypoints of the same application. The theme has application scope. We would have a problem if a theme contribution would affect other applications, but this is not the case with the demos. BTW, Nick is about to fix the theme contribution for the examples demo to use only custom variants, so that it will not affect the controls demo anymore. Generally, a theme contribution should define custom variants to prevent messing up other entrypoints. (In reply to comment #1) > I don't see the problem. Controls demo and examples demo are two entrypoints of > the same application. The theme has application scope. We would have a problem > if a theme contribution would affect other applications, but this is not the > case with the demos. Agree. Closed as INVALID. |