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
It always reflects on the base_class, so that and all the inheriting get all the associations. This causes issues where hyper-model is trying to instantiate associations on the client, but they don't exist on that class but maybe its sibling's class the an error is thrown and the page goes blank.
I'm thinking this was done before STI was implemented and the type column was looked at and used. But since that has been implemented, this should be fixed so that only the proper associations are reflected on and used.
This is only an issue when using STI classes that have their own associations.
An example:
The code that is doing this is
It always reflects on the base_class, so that and all the inheriting get all the associations. This causes issues where hyper-model is trying to instantiate associations on the client, but they don't exist on that class but maybe its sibling's class the an error is thrown and the page goes blank.
I'm thinking this was done before STI was implemented and the
type
column was looked at and used. But since that has been implemented, this should be fixed so that only the proper associations are reflected on and used.A fix would be
Run locally, all specs pass.
The text was updated successfully, but these errors were encountered: