Nick Sutterer
Nick Sutterer
I have trouble understanding why one would need both **naturally exclusive** options at the same time? Can you make a more elaborated example, please? :sunglasses:
Still struggling.. how do you decide what wins over what when you provide both values?
I understand that, but the problem is speed. My code is optimised and doesn't do any unnecessary lookups because I simply say "either in- or exclude". You might think this...
See, and suddenly understand what you want! :smiley:
So, `?fields="shipments,-payments"` means: show `shipments`, only?
Ok, but that is a different semantic than "my" `:include`/`:exclude`. Mine is on a library level and is very simple to understand since mutually exclusive. Yours is _your application_ requirement...
Thanks for your explanation! I agree that options are better than a million representers, that's why I introduced that directive. I still don't get how "include A, exclude B" is...
This would create an invalid YAML document - how'd you use this?
When you say "JSON API", do you mean the `JSONAPI` module or a random JSON API?
It's not even released yet :grin: haha! Is everything else working as expected? I will get back to the Roar 1.1 release, soon. Why is this posted on Representable, then,...