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
Currently, meta only works if value is also set (i.e. only for identity requests). I'm thinking that a better way would be for meta to work for URL-based requests too and for request and response to be merged into meta. This would allow applications to add arbitrary metadata to any request and make it accessible to the component. I don't have a great use case of that off hand, but I like that it makes identity requests more "normal." The downside I see that meta currently allows any data type, but if we go this route, it would have to be an object. Thoughts?
The text was updated successfully, but these errors were encountered:
Allow clients to set the initial `meta` value on the request. This is primarily for transformations with identity requests, but this generalizes the pattern for all requests.
Delivers #42
Currently,
meta
only works ifvalue
is also set (i.e. only for identity requests). I'm thinking that a better way would be formeta
to work for URL-based requests too and forrequest
andresponse
to be merged intometa
. This would allow applications to add arbitrary metadata to any request and make it accessible to the component. I don't have a great use case of that off hand, but I like that it makes identity requests more "normal." The downside I see thatmeta
currently allows any data type, but if we go this route, it would have to be an object. Thoughts?The text was updated successfully, but these errors were encountered: