It could be possible via routes but it would be nice it the syntax were to
allow it. I stopped developing it because I though instead of reinventing
the wheel with this syntax we may want to support some standard. Is there
any?
On Sunday, 30 December 2012 00:01:03 UTC-6, DenesL wrote:
>
> Yes, from the docs it is clear that one could use such syntax but the idea
> is to hide it somehow.
> So instead of /pets/dog I want just /dogs
> Note that I am providing all parameters for the query in the pseudo-code
> {pet.kind.eq.dog} to avoid having another arg.
>
>
> On Saturday, December 29, 2012 12:45:36 PM UTC-5, Massimo Di Pierro wrote:
>>
>> you can say something like:
>>
>> "/pets[pet]/{pet.kind.eq}"
>>
>> and call /pets/dog or /pets/cat
>>
>> It is not documented because I am convinced this syntax is definitive. It
>> needs more etsting and as you suggest it may be richer.
>>
>> massimo
>>
>>
>> On Saturday, 29 December 2012 11:32:25 UTC-6, DenesL wrote:
>>>
>>> Hi all,
>>>
>>> is there any documentation (aside from what is said in the book) about
>>> the queries parameter in parse_as_rest?
>>> Some examples would be nice.
>>>
>>> Also, looking at the patterns, there does not seem a way to specify a
>>> subset in a pattern e.g. (pseudo-code)
>>>
>>> "/dogs[pet]/{pet.kind.eq.dog}"
>>>
>>> which would retrieve all dogs from the pet table.
>>>
>>> Regards,
>>> Denes
>>>
>>>
--
