kwin commented on PR #41: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/41#issuecomment-1354270703
> We must not repeat this bad experience. If developers cannot rely on the repo having the state as prescribed in repoinit there must be a lot of boilerplate code written by developerss how to it should deal with unexpected repository content. From my perspective this is the primary goal of repoinit (and executing this prior to any other code based on SlingRepository). If you cannot rely on that, that must be very explicitly stated in the documentation and kind of makes repoinit useless for most use cases (as then you can do as well do the changes manually in your 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
