-
Notifications
You must be signed in to change notification settings - Fork 749
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
Make /info/bidders endpoint consistent between Go and Java #1788
Comments
Sounds good to me. What should the behavior be if enabledonly parameter is not either true or false? Perhaps we should use the default, or another option is to return an error. |
Discussed with a few other folks. We currently prefer to validate |
this was released with PBS-Java 1.71 |
I implemented this for PBS-Go, but noticed the specifications had since changed to return a 400 if the new |
This is ok @SyntaxNode , but the spec changing was due to your request from April 7th. :-) |
Ah! I see. In that case I believe this is a misunderstanding. I didn't intend to make it required, but to validate the parameter only when its provided, such that: /info/bidders -> all bidders (backwards compatibility) |
Implemented in PBS-Go 0.177.0. |
As discussed in PBS committee, there's currently a difference between PBS-Go and PBS-Java in the /info/bidders endpoint.
As both use cases are useful, the proposal is to add a query string parameter (?enabledonly=true/false). This value has no default and will return HTTP 400 if not provided with body "missing enabledonly flag"
The results of the /info/bidders/BIDDER endpoint should include all the fields currently in the PBS-Go output:
The text was updated successfully, but these errors were encountered: