Daniel (dB.) Doubrovkine
Daniel (dB.) Doubrovkine
Aha. If both values have a default it already violates `exactly_one_of`, but maybe if one of them has a default and you don't pass anything, then it should work?
Correct. A default of `nil` is still a default. Maybe rewrite the title of this issue to say something like the above scenario should not even load and produce an...
If neither param is provided then both get the default value and those are mutually exclusive, which errors by design. LGTM.
I understand this is not the way it behaved before, but I would say that this was a bug, fixed since. We probably didn't even have specs for this, hence...
Now that we have more attention on this issue, I think we should close this. IMHO it behaves as intended. Taking this back. An API with mutually exclusive and default...
This sounds like a valid scenario. Should we add an `unknown` or `undeclared` helper? Want to give this a try @lvonk?
I think both features would be valuable, and failing would be built on top of extracting the names of such parameters.
Looks like a big indeed. I bet we check for the class of whatever is inside the array. There's probably some other bugs like this with other types inside the...
So it looks like a bug because we explicitly document `You can override this process (content negotiation) explicitly by specifying env['api.format'] in the API itself.` Since you already have a...
Thanks for the analysis @jsteinberg.