-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fix initial polymorphic attribute #5366
Conversation
The goal here is to do as little work as we can with relationship payloads until the relationship is actually accessed. In an extreme case, where many relationship payloads are pushed, but no relationships are accessed, all we want to do is stash the payload.
@hjdivad would you have time to review this pr? |
Would you mind adding a regression test, to help ensure we don't make this mistake again... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on the change but would like to see a regression test added
The thing is I don't even know if this property is used at all. I think (maybe wrongly) if it was used, some existing tests would already be failing. I will investigate more asap. |
@runspired Ok, I also removed the initialization of the |
Also, I'm sorry, I've created this branch against the repo itself, not mine... |
Thanks! so the TLDR for anyone following along was that our tests passed bc the extended class (has-many) also initialized |
Maybe I'm missing something, but it seems weird for a relationship to be polymorphic by default, right ?