You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we forcefully change the accessibility of object members in order to change private members of those objects.
Asked JetBrains to expose a setter function so that we don't need to do that stuff anymore. If they add support for that, we should change our code to use that.
If not we could try to keep searching for a way to achieve the same result without force-accessing fields.
As long as we forcefully access private fields in our solution, those fields could be changed upstream and our code would break without prior notice.
The text was updated successfully, but these errors were encountered:
Currently we forcefully change the accessibility of object members in order to change private members of those objects.
Asked JetBrains to expose a setter function so that we don't need to do that stuff anymore. If they add support for that, we should change our code to use that.
If not we could try to keep searching for a way to achieve the same result without force-accessing fields.
As long as we forcefully access private fields in our solution, those fields could be changed upstream and our code would break without prior notice.
The text was updated successfully, but these errors were encountered: