fix: via resource class returns model classes vs resource classes

[adrianthedev]

Description

Fixes an issue where if you had multiple resources representing a model, in some areas of your app, the first resource in an alphabetical order would get assigned instead of the proper one.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

Manual review steps

1. Enable z_posts (named like this to ensure it will be the last alphabetically) resource in the sidebar
2. Navigate to one post
3. go and navigate to a PhotoComment (below).
4. observe that the breadcrumbs point to z_posts (not posts)

Manual reviewer: please leave a comment with output from the test if that's the case.

[codeclimate]

Code Climate has analyzed commit 865579a and detected 0 issues on this pull request.

View more on Code Climate.

[adrianthedev]

Hey @bear-in-mind. This was easier than expected. Can you give it a try and see if this fixes your particular issue? This will definitely fix more issues from the past and down the line.

[bear-in-mind]

Thank you so much Adrian ! Will give it a go early afternoon :)

[adrianthedev]

Awesome! You might need to run rails avo:build-assets if you use it off GitHub.

[bear-in-mind]

So indeed, a few issues seem to be solved by your changes, including the one I showed you with the breadcrumbs 😎

However the Back button in nested resources is still referring to the wrong parent resource. Here's a screenshot (sorry, it's in French...):

[adrianthedev]

🙌 Fixed that as well. The global association_resource finds the proper resource now.

[bear-in-mind]

Works greaaaaat 🙏🙏🙏
Thank you so much Adrian !

[github-actions]

This PR has been merged into main. The functionality will be available in the next release.

Please check the release guide for more information.