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
we have so-called domain objects that come from the server, we, at the client side, can't really rename them without breaking the contract with the server, so doing renaming always imposes some risk, this risk could have been avoided if there was a way to lock an interface from unintended renamings
The text was updated successfully, but these errors were encountered:
are these defined in a .d.ts or in a .ts file? if .d.ts then this falls under the same umbrella as #7458 and #8227. the fix for these is not to rename symbols coming from a declaration file unless you are editing this file directly.
we have so-called domain objects that come from the server, we, at the client side, can't really rename them without breaking the contract with the server, so doing renaming always imposes some risk, this risk could have been avoided if there was a way to lock an interface from unintended renamings
The text was updated successfully, but these errors were encountered: