When using the override nested properties functionality as part of extensions, most of it works as expected. We’re able to override just the label, or the definition, and use almost all the other inherited parameters. However, it seems to automatically override hidden: true so that it’s false, even if I don’t touch that parameter. Is this a bug?
Hi Anya,
Thank you for your feedback. This is classified as a bug on our side and we are actively fixing it.
Meanwhile, please re-declare the hidden field to true as a workaround.
Our apologies for this inconvenience.
1 Like
Hi Phien,
Thanks for the info. Since a few weeks have passed, I was curious if you have any thoughts on when this bug fix might be released?
It’s not urgent since it’s more about code maintainability rather than customer-facing functionality, but we have some PRs/branches ready that make use of nested parameter inheritance to clean up a LOT of code. Since you said the team is actively working on a fix, we decided to hold off on the work so we can do it all at once. Would love to finish that work off if possible! Appreciate any updates.
Thanks,
Anya