Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support custom actions as a first-class entity #2743

Open
jesseduffield opened this issue Jan 6, 2025 · 0 comments
Open

Support custom actions as a first-class entity #2743

jesseduffield opened this issue Jan 6, 2025 · 0 comments

Comments

@jesseduffield
Copy link

Copied over from #222 (comment) (forgive me not using the specified template)

I've been taking a look at Administrate as an alternative to RailsAdmin and it looks like the ability to easily add custom actions is the main thing that's currently missing. In rails admin you can specify actions against models and those actions will show up next to the default routes like so:

image

You can implement each action either as immediately doing something upon clicking it, or having it first show a form and then doing something upon form submission.

Actions also automatically appear at the end of tables for easy access:

image

I think that actions should be considered a first-class entity in Administrate, just like they are in RailsAdmin, and I believe that Administrate can find a way to implement it that aligns with its value of using as much regular rails as possible.

I'm eager to switch over to Administrate because I much prefer its general approach to RailsAdmin but it sounds like this shortcoming is going to be too onerous to justify the switch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant