Skip to content

add a design time decorator that prevents properties from being renamed #11863

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
zpdDG4gta8XKpMCd opened this issue Oct 26, 2016 · 5 comments
Closed
Labels
In Discussion Not yet reached consensus Suggestion An idea for TypeScript

Comments

@zpdDG4gta8XKpMCd
Copy link

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

@RyanCavanaugh RyanCavanaugh added Suggestion An idea for TypeScript In Discussion Not yet reached consensus labels Oct 26, 2016
@mhegazy
Copy link
Contributor

mhegazy commented Oct 26, 2016

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.

@zpdDG4gta8XKpMCd
Copy link
Author

no, it's in a plain *.ts

@mhegazy
Copy link
Contributor

mhegazy commented Oct 27, 2016

so it does have an implementation packing it? or is it just some interfaces?

@zpdDG4gta8XKpMCd
Copy link
Author

it has an interface declaration + auxiliary functions like create, areEqual and copy

@RyanCavanaugh
Copy link
Member

Closing due to low feedback volume

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
In Discussion Not yet reached consensus Suggestion An idea for TypeScript
Projects
None yet
Development

No branches or pull requests

3 participants