We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
EntitiesResponse and EntityObjectResponse share a common set of attributes, getter/setters for error and extensions.
Testing the result of handleFroidRequest is more complex than it needs to be. use-case - logging errors.
Define a common interface that provides accessors for errors and exentions.
Please briefly describe which alternatives, if any, have been considered, including merits of alternate approaches and tradeoffs being made.
Please provide any other information that may be relevant.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Problem Statement
EntitiesResponse and EntityObjectResponse share a common set of attributes, getter/setters for error and extensions.
Testing the result of handleFroidRequest is more complex than it needs to be. use-case - logging errors.
Proposed Solution
Define a common interface that provides accessors for errors and exentions.
Alternatives Considered
Please briefly describe which alternatives, if any, have been considered,
including merits of alternate approaches and tradeoffs being made.
Additional Context
Please provide any other information that may be relevant.
The text was updated successfully, but these errors were encountered: