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.

Sign up for GitHub

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

Jump to bottom

Generalise error messages #112

Closed
csarven opened this issue Nov 6, 2019 · 2 comments
Closed

Generalise error messages #112

csarven opened this issue Nov 6, 2019 · 2 comments
Labels
topic: resource access

Comments

@csarven
Copy link
Member

csarven commented Nov 6, 2019

If possible generalise the solution to cover status messages for both client ( #28 ) and server ( #111 ) errors.
@csarven csarven mentioned this issue Nov 6, 2019
Open
@csarven csarven mentioned this issue Mar 18, 2020
Closed
@csarven
Copy link
Member Author

csarven commented Jun 22, 2020 •
edited
Loading

See also solid/data-interoperability-panel#29 as possible input for this issue.

@csarven csarven mentioned this issue Jun 22, 2020
Open
@csarven csarven added this to the ~Candidate Recommendation milestone Jun 22, 2020
@csarven
Copy link
Member Author

csarven commented Jun 22, 2020

At this time, server error details are not needed: #111 (comment) . So, any possible generalisation may depend on the data model that can also cover server-specific information.

@csarven csarven closed this as completed Jun 22, 2020
@csarven csarven removed this from the ~Candidate Recommendation milestone Jun 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic: resource access
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@csarven