fix: fixed selected component

[JamalAlabdullah]

Description

• Added selected component id to be selected and presented in selector for column in subform.
• Added test

Related Issue(s)

• The selected component does not remain selected #14259

Solution After:

Screen.Recording.2024-12-19.at.10.55.01.mov

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.57%. Comparing base (1aa8bb1) to head (3dd663e).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #14315   +/-   ##
=======================================
  Coverage   95.57%   95.57%           
=======================================
  Files        1841     1841           
  Lines       23880    23882    +2     
  Branches     2755     2756    +1     
=======================================
+ Hits        22823    22825    +2     
  Misses        800      800           
  Partials      257      257           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[lassopicasso]

I was initially thinking along the same lines as you to identify the component. However, as @mlqn pointed out for me earlier, using the title has some potential flaws—for example, if multiple components share the same title. Additionally, the new feature from #13980, which allows users to customize the table column title (tableColumn.headerContent), will break this logic since it separates the column title from the component's title. Given this, we might need a different approach to ensure correct component identification

[JamalAlabdullah]

I used id instead of title , what do you think?

[lassopicasso]

That is a better approach I think, however I don't think componentId is supported in the app. As you can see in the preview below. If there are not other approaches or props to be used here to identify, perhaps you could contact team apps in altinn-studio-channel and describe them this problem for studio whereas if they can allow a prop such as componentId to be set in the tableColumns.