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
The order of requiring gems shouldn't matter #2
Comments
This happens because that's what repository is doing now and it's a bit ugly. We should probably introduce a setup specific for repository which will take care of extending relations. I don't see any other way. Check out #1 too, it's related. |
This is now fixed. All plugins have been extracted to rom and rom-sql. |
Wooooo, thanks Piotr! |
@jaredbeck :) I'm gonna push a release in a couple of days |
Hi, I am just getting started with ROM and when I tried out the memory adapter I got the same error with attributes not found:
I'm not sure if I am doing something wrong ... here is my code:
I figured out how to get it working by adding the following lines to the
I figured this out by trial and error and not at all sure if this is helpful or not as I don't really (yet) understand the design intent of the classes involved. Do you have any suggestions for me to get this working without having to edit the And thanks for moving forward with ROM. It is an ambitious effort and I am thrilled you are tackling it. P.S. I have attached my Gemfile.lock in case it helps. |
@dwhelan sorry about that, I didn't make it anywhere clear that currently only rom-sql works with repositories out-of-the-box. I'll add a list of supported adapters to the docs. |
@solnic Thanks for the quick response. |
I'm following the repository guide (http://rom-rb.org/guides/basics/repositories/) as closely as I can, but I get an error on the first example.
Changing the order of the gems in my Gemfile seems to do the trick though. The following seems to work.
Ideally, gems can be required in any order. If that can't be achieved, this problem is going to confuse a lot of people.
Thanks, I'd offer to help, but I'd be in way over my head. :)
The text was updated successfully, but these errors were encountered: