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
Re-enable inferrence if/when we agree as a team #13
Comments
socsieng
pushed a commit
that referenced
this issue
Jun 16, 2020
Need to discuss with the rest of the team about whether or not this logic should be introduced. Issue #13 has been raised to track this.
socsieng
pushed a commit
that referenced
this issue
Jun 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code that inferred request parameters based on the presence of other values was removed to keep the button API consistent with the
loadPaymentData
request parameters.The downside to this is that unless developers read the API documentation, exploring the API and just trying things out could increase the chances that the user receives an error.
I would like to revisit this and re-enable this type of inference if we can get consensus on this approach.
The text was updated successfully, but these errors were encountered: