AAE-24018 Readonly dropdown with the rest config don't fetch options when form rule change it to not readonly

[wiktord2000]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation
• Other... Please describe:

What is the current behaviour? (You can also link to an open issue here)
AAE-24018

Screen.Recording.2024-07-18.at.13.32.02.mov

Note: We have form rule here: Enable dropdown when Text field has '1', otherwise is disabled.

What is the new behaviour?

Screen.Recording.2024-07-18.at.13.32.42.mov

Note: We have form rule here: Enable dropdown when Text field has '1', otherwise is disabled.

Does this PR introduce a breaking change? (check one with "x")

• Yes
• No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

[wiktord2000]

Note: With the current code is difficult to call api only when field is not readonly by the applied rule (it would be ideal I guess), so the call is done at the form init even the dropdown is readonly at that time.

[wiktord2000]

The actual issue refers to cloud widgets but I guess I have to update regular ones as well, I can remove the changes if I'am mistaken (dropdown.widget.* files)

[kathrine0]

Note: With the current code is difficult to call api only when field is not readonly by the applied rule (it would be ideal I guess), so the call is done at the form init even the dropdown is readonly at that time.

Can't we track the readonly value change and query the api only then? Why is it not possible?

[wiktord2000]

Note: With the current code is difficult to call api only when field is not readonly by the applied rule (it would be ideal I guess), so the call is done at the form init even the dropdown is readonly at that time.

Can't we track the readonly value change and query the api only then? Why is it not possible?

After small investigation, we relay on @input() field from inherited component class -> WidgetComponent, and readonly state is determined by field.readOnly property (when this rule will be fulfilled this value will change), I tried to use ngOnChanges hook on that but seems that we still relay on the same reference hence we can't track its changes. The benefit of current implementation is that we always call once when we will call every time readonly has changed it could lead to multiple api calls, which are not needed

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud