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

Resource Interface #9

Closed
leogr opened this issue Nov 10, 2017 · 0 comments · Fixed by #28
Closed

Resource Interface #9

leogr opened this issue Nov 10, 2017 · 0 comments · Fixed by #28

Comments

@leogr
Copy link
Collaborator

leogr commented Nov 10, 2017

Structured and Mapped Resources are different but should be identical for consumers.

For instance, ListResponse needs to use both but currently cannot.

Also, a Resource Interface could totally de-couple core and resource packages.

Since core needs to use Resource Interface it should be defined in the same package, then core could implement it for Structured and resource for Mapped.
Furthermore, third-party could use it to implement other kinds of resource.

However, the two kinds are using attributes in different ways actually I have no clear ideas how the interface should be.

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

Successfully merging a pull request may close this issue.

1 participant