Querysting path criteria cannot manage depth
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 57
- Forks
- 103
- Avg merge
- 10h 25m
- Merged PRs (30d)
- 18
Description
At the moment, when we create a collection, if we want to restrict the results to a given folder contents but exclude its sub folders contents, we have to enter the depth manually as an integer with the :: separator, like this:
../news::1
The querystring widget should provide a way to do it easily.
The question is how:
- shall we provide a input field so the user can enter an integer ?
- shall we provide a "Search Sub-Folders" checkbox (like the old Topic Path criterion used to do) ?
@vangheem do you know if the UI team already discussed that ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the querystring widget and the old Topic Path criterion's "Search Sub-Folders" behavior. Determine with the UI team whether depth should use an integer input or a checkbox, then define the expected querystring output and verify that the chosen control supports restricting results to a folder without its subfolders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100