rails g avo:all_resources should work only for models that inherit from ApplicationRecord

[yshmarov]

In my app I have a few "virtual" models:

• https://github.com/yshmarov/moneygun/blob/main/app/models/membership_invitation.rb
• https://github.com/yshmarov/moneygun/blob/main/app/models/organization/transfer.rb
• or models/current.rb

Currently running rails g avo:all_resources also creates empty resources like app/avo/resources/membership_invitation.rb & others

Expectation: create resources only for database-backed models

[colinross]

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.

[yshmarov]

@colinross I kinda agree. the "issue" is not worth solving