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
[WIP] Setcontent for front #488
Conversation
…tryxx/refactor/setcontent-for-front
…tcontent-for-front
…tcontent-for-front
…tcontent-for-front
…tcontent-for-front
…tcontent-for-front
Good to see you back in action on this! 👍 |
I happy too ;) I'm back with full bag of good (imo :P) ideas ;) |
I haven't commented much on this, but that doesn't mean i'm keeping an eye on it. ;-) Just let me know when you think it's done, or ready for a second pair of eyes. 👍 |
Thanks Bob, I'm going to let you know ;) It comes to the end ;) |
…actor/setcontent-for-front
…tcontent-for-front
…tcontent-for-front
04ab437
to
67c69fa
Compare
…tcontent-for-front
…ur into stryxx/refactor/setcontent-for-front
…tcontent-for-front
…tcontent-for-front
…tcontent-for-front
…tcontent-for-front
This PR has been lingering for two and a half years now. I think it's time to close it. 😔 |
Checklist copied from #116. API won't be 100% the same, but functionality should be kept.
Basic
{contenttype}
{contenttype}/first/{number}
{contenttype}/last/{number}
{contenttype}/random/{number}
random
is not going to work with Doctrine ORM queries, see answer on Stack Oveflow for info.{contenttype}/{id}
- it cannot be supported becauseid
is not unique for every of contenttype.id
is unique globally, so it not possible to get correctcontenttype
byid
.{contenttype}/{slug}
WHERE
{key}: {value}
{key}: {operator}{value}
where operator is one of%
<
<=
=
warning Currently the operations will not work for numbers/dates/etc. because of JSON-encoded values.
WHERE advanced
{key}: {value1} || {value2}
or{key}: {value1} && {value2}
"{key1} ||| {key2}": "{value1} ||| {value2}"
{key}: 'now'
and other special datetime selectors (e.g.now
,today
,yesterday
,last year
,next thursday
).Special
limit {number}
orderby {field}
ororderby -{field}
warning This works for fields that have only a single value (think of it as a column)
Multiple sortorders (comma-separated)
returnsingle
printquery
- I'm not sure if we should have this optionwarning Currently shows DQL. Let's see if we can show a runnable query instead.
Advanced
Pagination and Search are not implemented yet.
allowpaging
{contenttype}/search/{num} where filter: {term}
{ct1},{ct2},{ctN}/search/{num} where filter: {term}
Misc
New feature