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

The nested relationship model is often not yet available in the parent object observer created() method #129

Open
scadh opened this issue Jan 29, 2021 · 0 comments

Comments

@scadh
Copy link

scadh commented Jan 29, 2021

I am experiencing an issue where my parent object and nested relation are both saved correctly to their respective tables, but the parent model object passed to it's Observer created() method does not contain the nested relationship because it hasn't yet been created. The created() method passes the parent model off to an email mechanism that relies upon some data inside the child object and fails when that data evaluates to null. Is there any way to specify that the nested object(s) be stored first so that that parent relation method can find them? Or some other solution I could employ?

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