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

Extended configs appear to not be fixed #5678

Open
Timer opened this issue Nov 1, 2018 · 4 comments · May be fixed by #10014
Open

Extended configs appear to not be fixed #5678

Timer opened this issue Nov 1, 2018 · 4 comments · May be fixed by #10014
Milestone

Comments

@Timer
Copy link
Contributor

Timer commented Nov 1, 2018

#5645 (comment)

@babakness
Copy link

If my hack is exploiting a bug; why not enable some default that enables the use of absolute paths as a zero-config option in TS? Writing ../../../../foo/bar is tiresome.

@Timer
Copy link
Contributor Author

Timer commented Nov 2, 2018

Already tracking :-) #5118

@babakness
Copy link

Ah, ok thanks!

@xiaoxiangmoe
Copy link
Contributor

xiaoxiangmoe commented Nov 17, 2018

@Timer Can we not turn off this feature in special cases? For example, if the environment variable DANGEROUS_OPEN_TSCONFIG_EXTENSION=true or DANGEROUS_ALLOW_DISABLE_TSCONFIG_CHECK=true

@Timer Timer modified the milestones: 2.1.2, 2.1.3 Dec 23, 2018
@ianschmitz ianschmitz modified the milestones: 2.1.3, 2.1.4 Jan 4, 2019
@ianschmitz ianschmitz modified the milestones: 2.1.4, 2.1.5 Feb 10, 2019
@iansu iansu modified the milestones: 2.1.6, 2.1.x, 3.x Mar 6, 2019
@iansu iansu linked a pull request Jun 30, 2021 that will close this issue
5 tasks
@iansu iansu removed the issue: bug label Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants