You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I agree it should not pick up modules, I don't see it picking up a defined class that implements ActiveModel::Model as a bug, as this behavior is largely in-line with Ruby's approach to duck typing. What is the semantic difference between a resource and a model? In a traditional Rails app, they can be dealt with essentially interchangeably, correct?
That said, I'm not saying that you shouldn't be able to opt-in to some alternative behavior with some level of configuration, but my gut tells me the convention should be that if it's a resource to rails, it should be a resource to avo.
In my app I have a few "virtual" models:
models/current.rb
Currently running
rails g avo:all_resources
also creates empty resources likeapp/avo/resources/membership_invitation.rb
& othersExpectation: create resources only for database-backed models
The text was updated successfully, but these errors were encountered: