Do you have a roadmap for v2?

[goosys]

First of all, congrats on the v1 release — I’ve been waiting for this for a long time! 🎉🎉🎉✨✨✨🎂🎂🎂

I imagine there’s still a lot to do for the next steps, and I was wondering if you have any plans or a rough timeline for how development will move forward.

I rely on this library heavily in my application. For now I’m trying to avoid maintaining a heavily customized fork because I’d prefer to contribute upstream as much as possible. But if development continues at the current pace, I may need to reconsider that approach, so I wanted to get a better sense of the future direction.

I’d love to align my contributions with your plans, so any insight would be super helpful.

[nickcharlton]

Thanks! It contains many of your contributions from the last year or so, and I really appreciate the time you've put into it!

I think we can speed things up a bit now. I was concious of the lack of a v1 for sake of it being stable and not introducing too many big changes that would be a lot of work for people to work through. Once I balanced a few busy months of work, it took much longer than I hoped!

What do you want to see? Maybe this is a good place to start listing out some things you'd like to see (including your existing PRs?).

So far, my plan involves:

1. Dropping some of the older Ruby/Rails support which are EOL,
2. Continuing on with the acceptance testing PR

But I think these are just before v2 is ready targets to stick with semver.

[pablobm]

The milestones here look good. I'd start from there too. I also want to do another review of issues/PRs and sort them into groups or close them as I did last time. Additionally, a specific issue that I've been wanting to tackle for some time is #2361.

[pablobm]

Support creating small Dashboards for modals

I don't understand this one. Do you mean modal dialogs? Where would these appear?

[goosys]

a specific issue that I've been wanting to tackle for some time is #2361.

I want to solve this as well.
I’m working on a resolver that allows having multiple admin dashboards depending on roles, but I haven’t been able to extend it to support namespaced models yet.
I’m struggling with the automatic mapping between controller names, model names, and dashboard names--it doesn’t convert cleanly in all cases. I’d be really happy if we could get this resolved soon. 😄

[goosys]

Support creating small Dashboards for modals

I don’t have a concrete idea yet, but this is roughly what I have in mind.

If we could define smaller dashboards and keep controller action methods shared, while allowing only certain attributes to be edited or listed, it might become easier and more convenient to build partial UI components using things like turbo_frame.

class UserDashboard
  ATTRIBUTE_TYPES = [
   ...
  ]
end
module UserDashboard
  class ChangePasswordModal
    FORM_ATTRIBUTES = %i[ password ]
  end
end
class UsersController
  private
  def switch_dashboard
    @dashboard = UserDashboard::ChangePasswordModal.new if ~any_condition~
  end
end

[goosys]

@pablobm
I’ll organize my thoughts on the small dashboards topic and open a separate issue for it.

@nickcharlton @pablobm
Is there anything else I can help with next?
If there’s something I can move forward on, please let me know.