You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would useful to support APIs that offer supplemental "detail" endpoints (e,g, GET /resource/details) that accept one or more resource identifiers in bulk (request body data), rather than one at a time (e.g. GET /resources/{id}/details) as is the case in a traditional parent-child stream relationship. I don't really know enough about context or state here to fully understand the implications of something like this, but it feels possible.
The text was updated successfully, but these errors were encountered:
Feature scope
Taps (catalog, state, tests, etc.)
Description
I'm imagining something like
This would useful to support APIs that offer supplemental "detail" endpoints (e,g,
GET /resource/details
) that accept one or more resource identifiers in bulk (request body data), rather than one at a time (e.g.GET /resources/{id}/details
) as is the case in a traditional parent-child stream relationship. I don't really know enough about context or state here to fully understand the implications of something like this, but it feels possible.The text was updated successfully, but these errors were encountered: