Open
Conversation
Contributor
Author
|
Found another issue there. Also, found a bug: If you have a model inside a module, the plugin will ignore the module name. Gonna fix it soon |
Contributor
Author
|
Woops, sorry. That was just a misconfiguration on my side. However, the new patch would still be helpful, I believe |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses #20
Background: I'm extending Rails load paths to load models from directories other than
app. It wasn't possible to annotate models outside the defaultapp/modelsdirectory, so I've implemented itUnfortunately, I have absolutely no idea how to test it without a running Rails application, so I just manually tested it with my application and let it be
If you have any tips on how to test those things, it would be great