Skip to content
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

Suggestion: Add option to make generated files read-only #17560

Closed
GordonSmith opened this issue Aug 2, 2017 · 1 comment
Closed

Suggestion: Add option to make generated files read-only #17560

GordonSmith opened this issue Aug 2, 2017 · 1 comment
Labels
Out of Scope This idea sits outside of the TypeScript language design constraints Suggestion An idea for TypeScript

Comments

@GordonSmith
Copy link

On several occasions I have accidentally modified either the generated JS file, or the generated ".d." definition file.

Typically this happens inside vscode during a debug session, or within a chrome debug session. But it has also happened during regular edit/compile cycle (with the .d. file specifically).

@DanielRosenwasser
Copy link
Member

Hey @GordonSmith, while I've definitely done the same, we've avoided getting involved with file permissions. For a similar request, see #14726 where we've suggested for users to incorporate a post-build step.

@DanielRosenwasser DanielRosenwasser added Out of Scope This idea sits outside of the TypeScript language design constraints Suggestion An idea for TypeScript labels Aug 2, 2017
@mhegazy mhegazy closed this as completed Nov 20, 2017
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Out of Scope This idea sits outside of the TypeScript language design constraints Suggestion An idea for TypeScript
Projects
None yet
Development

No branches or pull requests

3 participants