This solution is excellent, but I have another question. When I created a container for the first time, it worked perfectly. However, when I had already created some container components, the radio buttons didn't add automatically. Should I write Groovy, or is there another solution

Hello, I am creating multiple forms which has radio button field which are common for all of them.How can I inject a radio button component into each form container to avoid recreating the same component for every new form.  I have asked related question here but still didnt get currect solutionhttp...

Thanks for answering , but this solution didnt work for my case, is it possible to inject a component via component policies? or is there any other solution for this issue?

Hello,In a form container component I would like to inject another component something like this <sly data-sly-resource="${'component' @ resourceType='my/component/path'}"></sly>Changes to the injected component's properties lead to HTML duplication. The duplication seems to be caused by a data-sly-...

Thank you for your response. Although this solution is good, the previous one is more suitable for my case

HelloCan I add localized descriptions to tags? If not, what are the alternative solutions?

In the third-level multifield, using richtext has led to excessive requests. Thank you for your advice

Hello, The dialog for the component, which contains three levels of nested multifields with approximately 150 filled items, experiences significant latency, taking around 10 minutes to open Upon inspecting the browser's Network tab while opening the dialog, and it seems like there are a ton of reque...

Hello I'm currently injecting an overridden Experience Fragment Component at core/wcm/components/experiencefragment/v1/experiencefragment into my page. I've set the fragmentVariationPath, and now I'm aiming to retrieve the properties of its parent component, core/wcm/components/experiencefragment/v1...

I didn't get the answer. I had trouble using experience fragments directly as dynamic includes. So, I tried something else. Instead of using the whole experience fragment, I just took out the part I needed for the dynamic include. Now, I can control things better and get the results I want