You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by ramboz <gi...@git.apache.org> on 2017/06/28 00:33:40 UTC

[GitHub] sling pull request #245: SLING-6986 - The ResourceResolver mock does not tes...

GitHub user ramboz opened a pull request:

    https://github.com/apache/sling/pull/245

    SLING-6986 - The ResourceResolver mock does not test the resource type hierarchy in isResourceType

    Create a simple improvement, where we check:
    - the `sling:resourceType` property on the resource
    - then fallback to the `sling:resourceSuperType` property
    - then fallback to the `jcr:primaryType` property
    
    Also adding a unit test for it.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ramboz/sling SLING-6986

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sling/pull/245.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #245
    
----
commit daaa3791647314645d6c535cd23eadb961a74387
Author: Julien Ramboz <ra...@adobe.com>
Date:   2017-06-28T00:30:35Z

    SLING-6986 - The ResourceResolver mock does not test the resource type hierarchy in isResourceType

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] sling pull request #245: SLING-6986 - The ResourceResolver mock does not tes...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/sling/pull/245


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---