Data model: Design how to group subschemas

[Febakke]

Description

We need to include the JSON specific keywords used for combining schemas JSON documentation AllOf (Alle i) AnyOf (Noen i) OneOf (En i)

These keywords are in a way arrays, but each index can contain almost anything. This will cause some challenges with how our rightside menu should act.

Proposed solution Each "index" will have their own node in the tree-structure. Since they cant have any names we will call them "delskjema". We might want to include some information about type so it is possible for app developer to differentiate between them. In our GUI the user needs to choose a type for all subschemas, but this is not rule from JSON so we also have to handle subschemas with no type description.

• [ ] Decide how to split delskjema and type (delskjema - type : Tekst)

Right side menu The user can add subschemas and choose type for each. This should be included in a tab called "delskjema"

• [ ] Decide what the dropdown menu should include. a) All types and reference b) the user choose between two choices. Either the subschema is a type or it is a reference.

• [ ] Remove or keep the name field in the groupings "egenskaper" tab?

Delskjema If you focus/click on one of the children of the grouping they will behave as any other type except they do not have a name. So the name field should be removed.

Screenshots

Figma Can create prototype if it would help explain the concept

Considerations

• We will not support grouping as a restriction in this design

Ops requirements

Are there any requirements for monitoring? What is being built and what could go wrong? Are there any requirements related to backup?

Acceptance criteria

Describe criteria here (i.e. What is allowed/not allowed (negative tesing), validations, error messages and warnings etc.)

Specification tasks

• [ ] Development tasks are defined

Development tasks

Add tasks here

Test

Add test cases here as checkboxes that are being tested as part of the changes.

Definition of done

Verify that this issue meets DoD (Only for project members) before closing.

• [ ] Documentation is updated (if relevant)
  • [ ] Technical documentation (docs.altinn.studio)
  • [ ] User documentation (altinn.github.io/docs)
• [ ] QA
• [ ] Manual test is complete (if relevant)
• [ ] Automated test is implemented (if relevant)
• [ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)

[RonnyB71]

Possible duplicate of #6732.

[nkylstad]

Closing this issue as stale.