Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "excludePaths" per path #23

Closed
jdigger opened this issue Apr 17, 2015 · 2 comments
Closed

Add "excludePaths" per path #23

jdigger opened this issue Apr 17, 2015 · 2 comments

Comments

@jdigger
Copy link
Member

jdigger commented Apr 17, 2015

Something like

{
    "path" : "/content/someContent",
    "excludePaths" :
        [
            "subPath1",
            "subPath2/xyz"
        ],
}

To keep things clear/simple, the excludePaths should only allow relative paths to the path for that block. For example the following would be illegal:

{
    "path" : "/content/someContent",
    "excludePaths" :
        [
            "/content/otherContent",
            "/content/someContent/apath"
        ],
}

An open question: Should "." be legal?

@sagarsane
Copy link
Contributor

I guess . would effectively be a no-op right (especially if we only allow sub-paths)? If so, I think we could go eitherway. Legal or Illegal.

@jdigger
Copy link
Member Author

jdigger commented Apr 21, 2015

To work with specifics; given the following path structure:

/a
/a/b
/a/c

How would you express the following?

  1. Get everything in /a
  2. Get all children under /a, but not /a itself
  3. Get only /a itself, not its children

I expect it would like

  1. { "path": "/a" }
  2. { "path": "/a", "excludePaths": ["."] }
  3. { "path": "/a/." } or { "path": "/a", "excludePaths: ["*"] }

@masroormohammed masroormohammed mentioned this issue May 1, 2015
3 tasks
@jdigger jdigger closed this as completed Jun 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants