Qute: allow user project (or build-items) to override other templates with same id

[ia3andy]

Description

Currently having templates with same id result in an exception.

It would be nice to allow overriding templates provided by extensions or libraries in the Quarkus application.

Implementation ideas

No response

[mkouba]

Hm, so what should be the rules like? A template from the root application archive overrides templates provided by dependencies/extensions?

(or build-items)

In the sense of a TemplatePathBuildItem where the template is not backed by a file?

We could assign a priority to all discovered templates (e.g. root=5, dependency/extension=3, TemplatePathBuildItem=custom value), then identify the highest priority and fail if multiple templates for the same path define this priority. But it could be quite confusing. ALso it would be a breaking change. So we have to be careful.

[ia3andy]

add a new property: quarkus.qute.fail-on-duplicates and keep it to true by default, then your priority idea seems like a good option

[mkouba]

add a new property: quarkus.qute.fail-on-duplicates and keep it to true by default, then your priority idea seems like a good option

I don't think it's a good idea. From my exprience, non-default options are rarely used. OTOH it's a good idea to add a switch that can be used to revert the original behavior, i.e. quarkus.qute.fail-on-duplicates=false by default.

[ia3andy]

@mkouba any update on this?

[mkouba]

I'm struggling to define the priority assignment rules. For example, I can imagine a use case where a template from src/main/resources/templates should always take precedence...

[gbourant]

There is also #41449 and #43749 which may overlap with this :-)