Skip to content
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

WIP feat: error groups #245

Closed
wants to merge 1 commit into from
Closed

WIP feat: error groups #245

wants to merge 1 commit into from

Conversation

BelfordZ
Copy link
Member

@BelfordZ BelfordZ commented Dec 20, 2019

fixes: #225

It does have some implications on tooling - tooling would need to parse these refs, as well as union the errors based on their error code.

This is slightly departed from regular pattern of components being 1-to-1 with Foo-Object where foo is something like method, content descriptor, etc. If we have an ErrorGroupsObject, it would be a lie, since its an array. So this would introduce a ErrorGroupsArray, and then you ask, why would we ever put an error group in a method... its entire purpose is reuse. That took me full circle back to this. It seems the most simple, and the least in your way if you dont care about it.

@github-actions github-actions bot added the spec label Dec 20, 2019
@BelfordZ BelfordZ changed the title feat: error groups WIP feat: error groups Dec 20, 2019
@stale
Copy link

stale bot commented Feb 18, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot easily define server errors generic to all methods
1 participant