link_to_record: true, remember ?via_record_id=xxx&via_resource_class=yyy

[pjmuller]

Feature

see https://www.loom.com/share/eb42935e2725476f945e60b79ff84d40

When clicking on rows within an association and you have the link_to_record: true,
we go the right record ✅ but forget the association ❌ which makes the user experience inconsistent
This is especially the case with the global config.click_row_to_view_record = true which does the right thing on all non belongs-to columns, but forgets about the via_record_id parameter on belongs_to fields...

# resource 1 (table)
field :columns, as: :has_many

# resource 2 (columns)
def fields
        field :foobar, as: :belongs_to, link_to_record: true # correctly will open the `column` resource (i.s.o. foobar) yet forgets about the table (resource 1)
end

Current workarounds

switch all :belongs_to to :text and format_using in !view.form? but feels very dirty

[github-actions]

This issue has been marked as stale because there was no activity for the past 15 days.

[Paul-Bob]

Hi @pjmuller thanks for the details and the loom

When clicking on rows within an association and you have the link_to_record: true,
we go the right record ✅ but forget the association ❌ which makes the user experience inconsistent

When you mention that it makes the user experience inconsistent, are you specifically referring to losing context when the back button is clicked?

We're currently working on an approach (here) to enhance the functionality of the back button without relying on all the via parameters. I'm asking this to determine whether we can merge these issues or if you need those parameters to implement any custom logic that depends on them.

Thank you