The container component serves as a powerful tool for organizing other components within your application. Similar to layout components like panels and field sets, it groups related elements together. However, it goes beyond mere visual arrangement. Let’s explore how the container component impacts data storage and retrieval in the backend using the example shown below:
Response data in a layout component (fieldset or panel)
data: {
"textField": "example text",
"textField2": "example text 2"
}
Response data in a container component
data: {
"containerName": {
"textField": "example text",
"textField2": "example text 2"
}
}
In most cases the fieldset component should be used to group component together without changing how the response data is stored. However, in some advanced scenarios the container is a great choice to help group response data together when you need to access this data in JavaScript or downstream workflow. In most scenarios this component should be used by power users.