If it is easier to update any part of your working record to accommodate new developments in thought or circumstance,

before_action -> { doorkeeper_authorize! :public }, only: :index

# authenticated :user, lambda {|u| u.role == "admin"} do # root to: "admin/dashboard#show", as: :user_root # end

You can also specify constraints as a lambda:

Would it be desirable to specify the new object in a block? That would make it somewhat symmetrical to how Hash.new takes a block as a default value.

I totally understand that there may be a majority still considering this a bad practice and thus keeping it disabled by default in production seem ok. But there could at least be an option to enable it for people who want to, no?

patch: -> { step Destroy.method(:tidy_storage), before: :delete_model }

However, it can be a PITA if you want to customize one of those deeply nested components and add or remove a certain step, for example.

Not being cancelable makes validating dialog content impossible - eg a login dialog or anything that takes user input. Of course, it's easy enough to get around - but I think this should be a requirement of a dialog.

[link](url){:target="_blank"} Works for jekyll or more specifically kramdown, which is a superset of markdown, as part of Jekyll's (default) configuration. But not for plain markdown. ^_^