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

Separating representation datasets #235

Open
tpluscode opened this issue Jun 29, 2021 · 0 comments
Open

Separating representation datasets #235

tpluscode opened this issue Jun 29, 2021 · 0 comments
Milestone

Comments

@tpluscode
Copy link
Member

In v1.0 all requests get combined into a single dataset. The purpose of that was to have an easy way to combine different resource representations and especially their API Documentation(s) for the purpose of discovering operations

In hindsight this proved problematic when trying to access the dataset directly because everything got combined, potentially thousands of combined resources.

Instead, I would like to keep even response separated and only combine them with API Documentations when accessing the Hydra terms such as supported operations and properties

@tpluscode tpluscode added this to the 2.0 milestone Jun 29, 2021
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

1 participant