Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checkboxes instead of radiobuttons in the List component #2629

Open
walldenfilippa opened this issue Oct 23, 2024 · 2 comments
Open

Checkboxes instead of radiobuttons in the List component #2629

walldenfilippa opened this issue Oct 23, 2024 · 2 comments
Assignees
Labels
kind/feature-request New feature or request

Comments

@walldenfilippa
Copy link
Contributor

Description

List component today

The List component with radiobuttons has one or more datamodelbindings that stores the values in selected columns.

 "dataModelBindings": {
        "name": "SelectedItem",
        "profession": "SelectedItemProfession"
    },

Image

New proposition

If we implement a property in the List component where developers can select radiobuttons (default) or checkboxes, we have to change the formatting of the datamodelbindings. Should the checkbox values be stored in an array of strings or objects? Here is an example of what it could look like using an object array with two attributes in the json file:

 "dataModelBindings": {
          "row": "rowId" {
              "column1": "column1",
              "column2": "column2"
               ...
          }
  }

Is this something that is supported by backend today?

TEMPORARY workaround

Image

Within the repeating group
Image

What we want to accomplish

Image

Additional Information

Requirments

  • It is essential that the component supports a large number of data from an external API. (We want to visualize up to 1000 different appOptions). The List component fulfill this requirement.
  • One row can hold one or more columns, where each column can be set to a datamodelbinding attribute.
  • The selected rows in the List component should be automatically or by logic (in dataprocessor) visualized in another component. (We currently visualize this data in a repeating group)

Additionally (can be done through workarounds without any additional functions)
The external API fetches data to the List component based on an input "search" field. If a user decides to search on a new word in the input field the options in the list component should be exchanged. If the user has selected rows in the previous appOptions list, they should still be displayed in the visualization component (in our case the repeating group).

@walldenfilippa walldenfilippa added the kind/feature-request New feature or request label Oct 23, 2024
@walldenfilippa walldenfilippa changed the title Checkboxes instead of radiobuttons in the List komponent Checkboxes instead of radiobuttons in the List component Oct 23, 2024
@olemartinorg
Copy link
Contributor

Related issue (we've talked about binding these checkboxes to a repeating group structure in the data model):

@olemartinorg olemartinorg moved this to 👷 In Progress in Team Apps Feb 6, 2025
@olemartinorg olemartinorg self-assigned this Feb 6, 2025
@olemartinorg olemartinorg moved this from 👷 In Progress to 📈 Todo in Team Apps Feb 7, 2025
@walldenfilippa
Copy link
Contributor Author

Altinn documentation (PR): Altinn/altinn-studio-docs#2030

@paal2707 paal2707 moved this from 📈 Todo to 👷 In Progress in Team Apps Feb 20, 2025
@paal2707 paal2707 moved this from 👷 In Progress to 🔎 Review in Team Apps Feb 20, 2025
@paal2707 paal2707 moved this from 🔎 Review to 🧪 Test in Team Apps Feb 27, 2025
@HanneLauritsen1967 HanneLauritsen1967 moved this from 🧪 Test to ✅ Done in Team Apps Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature-request New feature or request
Projects
Status: Done
Development

No branches or pull requests

3 participants