Pablo Brasero

And by all means: please add a test. A field in the example app would be ideal, as it also acts as an example and a quick way to play...

Related: https://github.com/thoughtbot/administrate/issues/1861 Both issues might be solved if we unified `valid_action?` and `show_action?`.

Ongoing work to fix this issue properly: https://github.com/thoughtbot/administrate/pull/1941

Yeah, I don't think there's a way to do this at the moment. Perhaps it would be a good idea to add a new option to the field that allows...

Yup, that's the sort of thing we would need. I think it could be done better if it accepted a `call`-able instead, like a lambda. This is what we already...

@purinkle, what is the current status of this PR? I see that you pushed some changes recently. I had a look at the code. I ran `bundle install` and it...

OK, I added the changes to `Gemfile.lock` as well as unignored `yarn.lock` and ignored some Yarn artifacts. The specs run green for me, let's see what CI's opinion of this...

Have a look at the documentation for [Pundit](https://github.com/varvet/pundit). A policy object typically includes the current user and the resource to be authorized. In Administrate, we have an `ApplicationPolicy` superclass, which...

Oh, wait. You say fields, not records! Apologies, I see now... I don't think there's a way to do it at the moment, no :thinking:

Thinking a bit about this, perhaps a way to achieve it would be to use different dashboards for different users. Say that you have a `User` model, and only admins...