got it

thanks for spitballing ideas with me

I love this kind of feedback!

no problem! it's great to be able to throw thoughts around like this. understanding how the team think about the software makes it easier to work with as well

i'll share stuff when i get around to working on the dashboards

is there any way to add related resources on creation time ? something like nested_attributes, I would reeeeally need that

We don’t have support for that roght now, but we’re totally supportive for community PRs

We can help you navigate the code and tests to add this awesome feature 💪

I'd really like to contribute on that feature, but sincerely I don't really feel like doing so when I pay a (quite expensive I must say) license.

Hey @important-terabyte-39911 I'm sorry you feel that way, and I appreciate your feedback. As is the case with most software licenses, they include a list of current features and a roadmap for future ones. We roll out updates to all users to fix bugs and security issues and add new features as they are developed and released. The Pro license does not include custom development going forward. Although our roadmap doesn't yet include the nested resources feature, it might get added if there is a significant number of requests from the community. Based on customer feedback, we're focusing on more pressing issues like the menu editor, settings screens, cards on more pages, improving the stability of the product, and a few others that will benefit the greater Avo community. Having the product source available opens it up to the same awesome community to allow it to better help itself with PR's for bug fixes and new features. We're incredibly grateful for those contributions and how they make this community and Avo more wholesome. Since we offer the possibility to use Avo on a trial basis or with the Community version, we usually don't offer refunds on the Pro license. However, if you feel Avo doesn’t fit your current needs at this point because of this one missing part, we can extend the courtesy of refunding your payment.

I started this discussion on the forum to better keep track of it https://github.com/avo-hq/avo/discussions/779

@User draft PR 👇 https://github.com/avo-hq/avo/pull/781

I still have a few kinks to iron out and write docs, but the cards are a lot more useful with these updates

Is there a happy path to building non-database backed forms, yet? I think that's the promise of 'Tools' -- something that could be used as a front end to workflows or other things that aren't truly resources. For example a workflow to signing up a new organization -- fill in 10 fields, hit go, and orchestrate 5 underlying tables in my controller or other business logic classes.

It's possible to do that hand building up the form, but it feels like something like an

Avo::BaseForm

could be super useful to inherit from, get all of the same fields that you get, but the "hard work" of building up the form is super minimal.

There isn’t official support for that now but there was a guide contributed by an user on how to use Avo for REST based models

I think you could hack it like that until we add support for custom form building

Cool! I'll check it out. Sounds like we'll be able use this. Thanks!

it's a bit cumbersome, but it might stick until we add that feature

amazing job! looks like a tidy approach!

Thanks! It solves the code duplication issues

Next, I’m working on bringing cards to the resource page

Hi @User ! Have a question. So on Avo 1.0 we had the ability to eject the profile view which allowed us to customize the profile menu (I used it for more than Sign Out) and the names that show up and so on. Is there a standard way we can do that on 2.0? I noticed it now lives under a sidebar_profile_component but unsure how we can eject/modify those or if it's possible at all. Great job by the way, v2 looks great and it's just awesome.

hey @blue-hospital-77159 yeah, it's a known issue. I made a ticket and will probably fix this week. please subscribe there to keep track of https://github.com/avo-hq/avo/issues/801

thanks for the compliment. I can't wait to see what you're going to build with it.

Oh ok, that's helpful, thanks for the quick turnaround! I'll subscribe to it.

We created a new category on GitHub Discussions called "Feature feedback". We're going to create a page for each major feature and we hope you'll use them to better send us your feedback, and ideas. We'll keep on using the GitHub Issues for... issues and bugs 🙂 https://github.com/avo-hq/avo/discussions/categories/feature-feedback

Is the menu editing documentation correct on the docs site? Or is that future looking? I get

undefined method 'main_menu=' for #<Avo::Configuration:0x00000001166f6f28

if I add this to my initializer:

config.main_menu = lambda {
    section I18n.t('avo.dashboards'), icon: 'dashboards' do
      all_dashboards
    end
  }

hmmm. that's my fault. it's not launched yet