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

use labels instead of is_a? to determine whether nodes are of appropriate type #839

Merged
merged 3 commits into from
Jun 19, 2015

Conversation

subvertallchris
Copy link
Contributor

This solves #717.

Rails reload! method was bumping heads with the @model instance variable in QueryProxy. I can't totally pin down why, will need to look at it more another time. In the meantime, this skips around the problem by just using labels to determine whether nodes are of the appropriate type.

No new tests, this is too specific to Rails and it doesn't add anything new, it ends up in the same place using existing methods.

subvertallchris added a commit that referenced this pull request Jun 19, 2015
use labels instead of is_a? to determine whether nodes are of appropriate type
@subvertallchris subvertallchris merged commit 7919a45 into master Jun 19, 2015
@cheerfulstoic
Copy link
Contributor

Oh, interesting, that probably makes sense. If I had to guess, reload! is probably destroying the constant and then creating it over again which would explain why it's two different objects

@subvertallchris subvertallchris deleted the association_class branch June 22, 2015 22:04
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

Successfully merging this pull request may close these issues.

2 participants