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

Responses #1

Open
Cayan opened this issue Nov 8, 2016 · 5 comments
Open

Responses #1

Cayan opened this issue Nov 8, 2016 · 5 comments
Milestone

Comments

@Cayan
Copy link
Contributor

Cayan commented Nov 8, 2016

We must define if we are going to support hypermedia responses.

There are few patterns available today, I can mention:

There is a really nice discussion about this topic on the siren repository: kevinswiber/siren#15

@igorsantos07
Copy link
Contributor

Maybe a simple response like { data: {...} } in 2XX and { error: {...} } on 4/5XX would do?

Requiring the implementer to use a pattern could scare some lighter frameworks/libraries that provide little support for that out of the box.

@Cayan
Copy link
Contributor Author

Cayan commented Nov 8, 2016

I believe this would be the best approach for a first spec.

@Cayan Cayan added this to the v2 milestone Nov 8, 2016
@HenriqueMatias
Copy link

Hey could we close this issue?

@Cayan
Copy link
Contributor Author

Cayan commented Nov 9, 2016

Lets keep it open for a possible discussion in the future.

I'll edit the README file with some simple response patterns.

@HenriqueMatias
Copy link

hey Guys
I need to know whats the answer pattern for post requisitions.

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

No branches or pull requests

3 participants