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

Remove tight java coupling #18

Open
necrophonic opened this issue Dec 20, 2017 · 0 comments
Open

Remove tight java coupling #18

necrophonic opened this issue Dec 20, 2017 · 0 comments

Comments

@necrophonic
Copy link
Contributor

The error report should be replaced with a proper RFC7807 standards compliant problem report https://tools.ietf.org/html/rfc7807 - see https://github.com/ONSdigital/sdx-evolution/blob/master/lib/api/problem.go

Shouldn't be tied to implementation details of a framework being used in a separate service - at the least, services should respond to plain HTTP headers and codes as laid out in the specification and not complain if they don't receive specific structures.

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

No branches or pull requests

1 participant