Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Validating precedence in template groups #4268

Open
vlada-shubina opened this issue Jan 18, 2022 · 1 comment
Open

Validating precedence in template groups #4268

vlada-shubina opened this issue Jan 18, 2022 · 1 comment
Labels
area: authoring Enhancements to the process of authoring, maintaining, and testing templates Priority:2 Work that is important, but not critical for the release triaged The issue was evaluated by the triage team, placed on correct area, next action defined.
Milestone
Backlog

Comments

@vlada-shubina
Copy link
Member

vlada-shubina commented Jan 18, 2022 •
edited
Loading

When working with template groups, one of the most common mistakes is same or missing precedence.

Consider the checks for the template group / when installing the template package to check if the template with same precedence is already installed inside same group.

However valid scenarios are:

  • the templates may have same precedence in case language is different
  • the templates may have same precedence in case type is different
@vlada-shubina vlada-shubina mentioned this issue Jan 18, 2022
Closed
3 tasks
@bekir-ozturk bekir-ozturk added this to the Backlog milestone Jan 24, 2022
@bekir-ozturk bekir-ozturk added the triaged The issue was evaluated by the triage team, placed on correct area, next action defined. label Jan 24, 2022
@vlada-shubina vlada-shubina mentioned this issue Oct 26, 2022
Open
@YuliiaKovalova YuliiaKovalova added Priority:2 Work that is important, but not critical for the release area: authoring Enhancements to the process of authoring, maintaining, and testing templates labels May 18, 2023
@vlada-shubina
Copy link
Member Author

vlada-shubina commented May 18, 2023 •
edited
Loading

This is a nice fit as validation check in scope of #2623
for authoring tools we may consider an extended check to check known templates in the template group for precedence clashes (for example using search cache for that, or other location for 1st party templates).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: authoring Enhancements to the process of authoring, maintaining, and testing templates Priority:2 Work that is important, but not critical for the release triaged The issue was evaluated by the triage team, placed on correct area, next action defined.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@vlada-shubina @bekir-ozturk @YuliiaKovalova