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

VSCode is difficult to configure if you use a different tsconfig for your tests and your production code #8033

Open
DanKaplanSES opened this issue Oct 10, 2023 · 1 comment
Labels
STATE: Stale An outdated issue that will be automatically closed by the Stale bot. TYPE: enhancement The accepted proposal for future implementation.

Comments

@DanKaplanSES
Copy link

What is your Scenario?

I've been asked to break up the trade-offs listed in #7978 (comment) into separate issues so they can be discussed individually.

What are you suggesting?

VSCode is limited to parsing a root tsconfig.json (at least, that's my interpretation of that linked issue). This can cause problems if your production code is written in typescript, too; how do you make sure VSCode uses the correct configuration for your testcafe test files and the correct configuration for your production files? VSCode will only use one tsconfig file at the root (unless you use project references).

What alternatives have you considered?

No response

Additional context

No response

@DanKaplanSES DanKaplanSES added the TYPE: enhancement The accepted proposal for future implementation. label Oct 10, 2023
@need-response-app need-response-app bot added the STATE: Need response An issue that requires a response or attention from the team. label Oct 10, 2023
@aleks-pro aleks-pro removed the STATE: Need response An issue that requires a response or attention from the team. label Nov 10, 2023
Copy link

github-actions bot commented May 9, 2024

This issue has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this issue in the future. If it still affects you or you have any additional information regarding it, please leave a comment and we will keep it open.

@github-actions github-actions bot added the STATE: Stale An outdated issue that will be automatically closed by the Stale bot. label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
STATE: Stale An outdated issue that will be automatically closed by the Stale bot. TYPE: enhancement The accepted proposal for future implementation.
Projects
None yet
Development

No branches or pull requests

2 participants