[14.0][FIX] only play onchange on editable field

[sebastienbeau]

solve issue when have limited access right (do not try to read none accesible field) solve perf issue by avoiding to compute computed readonly field

TODO

• [ ] write test case

[sebastienbeau]

@PierrickBrun

[sebastienbeau]

Hi I will be back soon on this point with test and real case. My initial issue it that I am using a user for an API with restricted access. When I play the onchange on partner it will compute field like "rma_ids", stock information... so at this end I request access to a lot of object. Do not merge yet, it's quiet experimental

[legalsylvain]

Hi. Well, logged with your limited user, can you create an item (without onchange_helper installed) ? If not, you should not have the possibility to do it with the module installed. At first glance, If an onchange requires access right, you should give the access to your user.

[github-actions[bot]]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.