-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add ActiveRecord-backed fixtures. #1105
Add ActiveRecord-backed fixtures. #1105
Conversation
|
||
has_many :comments | ||
belongs_to :author | ||
url :comments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Didn't someone suggest a convention for fixtures of something like
class Post < AR::Base
# stuff
class PostSerializer < AM::Serializer
# stuff
end
end
👍 except master doesn't have activerecord nor sqlite, right? |
You're obviously right! |
It sort of does by accident in dev... which is why I made #1090 |
d3d3878
to
e870f73
Compare
Fixed the deps. |
6470195
to
86b9aef
Compare
86b9aef
to
83f11ac
Compare
gem 'activerecord' | ||
gem 'sqlite3', platform: :ruby | ||
gem 'activerecord-jdbcsqlite3-adapter', platform: :jruby | ||
end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you're probably right that all the rails stuff above should be in a gem :test
group..
Cool @beauby this will be really helpful into new feature cc/ @NullVoxPopuli |
Add ActiveRecord-backed fixtures.
… pass, which caused by #1105"
They are namespaced inside
ARModels
to avoid conficts with PORO models (that we might want to namespace as well).