You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by GitBox <gi...@apache.org> on 2022/03/09 14:59:33 UTC

[GitHub] [sling-org-apache-sling-jcr-contentloader] stefanseifert edited a comment on pull request #12: SLING-11189 ensure all built-in content readers are registered before processing any bundle in this listener

stefanseifert edited a comment on pull request #12:
URL: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/12#issuecomment-1062999900


   I guess what I was hinting at was that the implied behavior when no requireImportProvider directive was provided could be backward compatible.  Meaning that if the file extension matches one of the configured "reader" file extensions (and no ignoreImportProvider value conflict), then the "requireImportProvider" value could default to that file extension and processing would be deferred until the expected reader arrived.


-- 
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-unsubscribe@sling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org