altinn-studio icon indicating copy to clipboard operation
altinn-studio copied to clipboard

analysis: Should table columns config use a pointer to a component, or be manually configured?

Open Jondyr opened this issue 4 months ago • 0 comments

Context

When configuring table columns for a subform compontent we currently have three fields that can be defined:

Image of a subform table in an app

Image

  • headerContent a text resource key, used for the heading of the column Image

  • query a pointer to the datamodel property that will be displayed Image

  • defaultValue default display value for query

Problem statement

What is the right balance beteween code complexity and UX simplicity?

Currently we have three proposals:

  • The user selects a component from the subform layout, which fills out properties by copying them over
    • This solution brings up a new problem, should changes to the component then be synchronized?
    • No sync: might be confusing to the end user, if they expect it to sync
    • Sync: might cause added complex coupling logic to an already complicated dependency system
  • Same as above, except we allow the user to override the config
    • This is mostly a discussion point for UX if the suggestion above is agreed upon
  • The user manually defines all properties and no connection/pointer to a component is made
    • This is the simplest to implement, but might be a hard concept to convey to the user?

Jondyr avatar Oct 24 '24 08:10 Jondyr