bdelacretaz commented on PR #41:
URL:
https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/41#issuecomment-1354480678
> I think the best way out is to create new instructions with the right
behaviour, deprecate the old instructions.
I agree that repoinit should stay strictly backwards compatible, but for
this specific case I think a _strict_ option on `create path` can do the job,
without having to create completely new instructions (at least at the grammar
level) and without requiring new configurations.
How about
create path [strict] (nt:folder) /one(mixin nt:art)/step(mixin
nt:dance)/two/steps
where `[strict]` is a new option, just for the `create path` statement, that
activates the new behavior that this issues aims to implement?
That might cause execution of different code in the `jcr-repoinit` module,
but at the grammar level it's a simple change, that IMO clearly expresses
what's going on.
Doing it this means having to change existing repoinit statements, but I
think it's safer than changing the behavior for existing code.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
