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

Hydrating all Customer entries, always #101

merged 7 commits into from Mar 6, 2019


None yet
2 participants
Copy link

bkuhl commented Mar 5, 2019

Change log:

  • CustomerRequest is deprecated, now that customers()->get() and customers()->list() will always provide embedded entities (Thanks @bob983 for that). It is deprecated and not removed to avoid breaking changes. Any applications that still use this object to eager load will not experience any errors, it will just be more performant behind the scenes.
  • HasOne relationships (e.g. Customer has one Address) are now properly hydrated (see #89). Fix involved addressing an TODO that was previously outstanding
  • Some usage examples have been added for $client->customers()

Once merged, this will become 2.0.4.

bkuhl added some commits Mar 5, 2019

@bkuhl bkuhl requested a review from tompedals Mar 5, 2019

Copy link

tompedals left a comment

Nice work!

@bkuhl bkuhl merged commit 85d19b5 into v2 Mar 6, 2019

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
continuous-integration/travis-ci/push The Travis CI build passed

@bkuhl bkuhl deleted the hydrating-hasone-entities branch Mar 6, 2019


This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.