This repository has been archived by the owner on Feb 19, 2022. It is now read-only.
Fix nested associations after a change in 0.10.0 #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Let's say we have a model
In the 0.10.0 it tries to constantize a class based on the association name itsself, which breaks if association name does not correspond directly to the class name. In this example it tries to find class
Logo
instead ofUsersArea::Logo
This change seems to have fixed that problem for us at least. It would be great if someone could verify in their project :)