Extend Views Setup Handlers add (entity-manager/record/edit)

[yuri]

Technically, monkey patching is almost the same as view-setup-handler. The main difference is that I know that there're view-setup-handlers supported in a particular view and I'm more reluctant to change internals of the view. It's a burden for me when a view supports view-setup-handlers. Do not expect them to be applied anywhere. It's more of a hack. Adding view setup handlers anywhere would be a big mistake for the product. Either customizations will constantly break after upgrade or we do not touch code to prevent "official-way" customizations from breaking.

I have already written about this issue before.

[rabii]

I am just trying to avoid monkey patching and wanted to stick with the official way to do things

I hope there will be an official way in the future

Thanks yuri

[yuri]

Chance is very low. We may end up with view setup handler for all views. In fact, view-setup-handlers do not differ much from monkey patching.

[rabii]

Currently using https://docs.espocrm.com/development...anager-params/ is very useful, however there is no way to extend the entity-manager/record/edit view so that one can show/hide extended parameters in the entity manager edit view based on certain conditions. e.g i have two params to add to the entity manager (bool: Archived) and (varchar: source)
Now i need to show the source params only if the archived is true. this is a basic example but what i am working on has more conditions and sometimes even need to check state of existing parameters e.g stars / kanbanViewMode etc

Is there any change to add this to the View Setup Handlers framework so we could control the behavior of those params.

Thanks