mirror of
https://github.com/jeffknupp/sandman2.git
synced 2026-04-25 16:45:50 +03:00
[GH-ISSUE #23] More REST query patterns #12
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
pull-request
question
refactoring
research
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sandman2-jeffknupp#12
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @filmackay on GitHub (Jan 19, 2016).
Original GitHub issue: https://github.com/jeffknupp/sandman2/issues/23
Just wondering what people's thoughts are on implementing more complex patterns for reading (joins and filters), along the lines of things like:
(http://sailsjs.org/documentation/reference/blueprint-api for some ideas)
At some point it is easier to parse the URL, rather than prepare every conceivable pattern. Thoughts?
@filmackay commented on GitHub (Jan 22, 2016):
Realised just now that filter, sort, pagination is already supported - just not documented, is that right - or are they placeholder / partial implementations?
@jeffknupp commented on GitHub (Jan 22, 2016):
Nope, they're fully supported. I'll be sure to update the docs as soon as I can.
@filmackay commented on GitHub (Jan 22, 2016):
What about join pattern: /table1/id1/table2/id2/table3
In this situation you really need to parse the URL, rather than pattern match on it with routes?