Closed kwin closed 5 months ago
IMHO this can be achieved by leveraging org.apache.sling.caconfig.management.multiplexer.ConfigurationResourceResolvingStrategyMultiplexer
with its getResourcePath(Resource contextResource, "sling:configs", <FQCN of annotated configuration annotation>)
.
This would also be useful to provide a better guidance to users lacking write permission in that location (by e.g. disabling the Save button and make all fields read-only)
provided PR #31: it both adds a (i) button to show the actual persist path, and also renders the config details dialog readonly if the current user does not have write permission to this path.
Currently only the context path is exposed per CAC Editor page
Next to it there should be the repository resource path being exposed where newly added properties would be persisted. This helps with figuring out permission issues.