Release 3.93.1 switch off rendering for hidden components to improve the performance

Help & Support đź’»
1

Hi,
Checking the 3.93.1-rc.0 version, the Not Rendered option, I see that if a modal is set as Not Rendered, you can’t assign values to it by JS until it is completely open.

Normally I reuse the same modal/Accordion… for multiple operations Create/Update or different actions and set by JS the data according to the action.

For example a modal with not Rendered set and a detail inside, this code does not work.
{{
ui.detail_not_render.setValue(state.init_data);
ui.modal_not_render.open()
}}

Another modal, with the Hidden parameter and a detail inside, works correctly.
{{
ui.detail_hidden.setValue(state.init_data);
ui.modal_hidden.open();
}}

Is there any way to assign the values dynamically via JS?, if the modal has the Not rendered value set. You can play with the On Open trigger and works, but it changes the logic and complicates the control of actions.

Thanks!!

1 Like
2

Hi @Chema
Let us check this first, and we’ll get back to you later

3

Hi @Chema,

Thanks for reaching out!
Not rendered components can’t be modified until completely open by design.
We’ve added a Hide mode feature exactly for such cases — not rendered components do not exist at all while hidden!

Our recommendation for “Not rendered” components’ population is OnInit action. I know that it will change the logic, but it will improve application performance :man_shrugging:

4

OK, Thank you for your clarification.

1 Like