Hydrated Responses on POST/PUT/PATCH about fuelsdk-php HOT 3 OPEN

Could you elaborate a bit more with an example?

from fuelsdk-php.

So in the samples currently, when the developer performs a POST/PUT/PATCH instead of returning back the newly (created/modified) complete object (this is where the term "hydrated" comes in) to the originating call...they developer has to make a second call to invalidate the original request.

If we added an invalidation method internally on the SDKs as well as performing an internal hydration request, that may be more user friendly.

Does that all make sense?

from fuelsdk-php.

Gotcha, my concern with that would be the number of extra calls. When you call POST, it would end up doing a GET as well to hydrate the response which adds a bunch of overhead. Lets run this idea past @tkauble

from fuelsdk-php.