When using the approach of passing Rodauth::Auth subclasses explicitly via the :auth_class option, the auth class would be configured already, so in this case it would be convenient to be able to skip passing the block when loading the plugin.
class RodauthMain < Rodauth::Auth
configure do
# ...
end
end
plugin :rodauth, auth_class: RodauthMain
I was thinking whether I should move this into Rodauth::Auth.configure, or still require the block when :auth_class is not passed in, so that it's not possible to set up a Rodauth::Auth subclass without the :base feature loaded. What are your thoughts on this?
When using the approach of passing
Rodauth::Auth
subclasses explicitly via the:auth_class
option, the auth class would be configured already, so in this case it would be convenient to be able to skip passing the block when loading the plugin.I was thinking whether I should move this into
Rodauth::Auth.configure
, or still require the block when:auth_class
is not passed in, so that it's not possible to set up aRodauth::Auth
subclass without the:base
feature loaded. What are your thoughts on this?