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.

Sign up for GitHub

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

Jump to bottom

It's difficult (or impossible?) to use a testcafe tsconfig file as a project reference #8034

Closed
DanKaplanSES opened this issue Oct 10, 2023 · 2 comments
Closed

It's difficult (or impossible?) to use a testcafe tsconfig file as a project reference #8034

DanKaplanSES opened this issue Oct 10, 2023 · 2 comments
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?

This is similar to the above, but reusing the same TestCafe tsconfig file as a [project reference][3] is challenging, impossible, or at the very least, undocumented by TestCafe. The only workaround I can come up with is a tsconfig file for testcafe's usage and another tsconfig file for vscode's usage. But this is a DRY violation, allowing your tsc/vscode compilation to get out sync with TestCafe's.

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
@github-actions GitHub Actions
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
@github-actions GitHub Actions
Copy link

We're closing this issue after a prolonged period of inactivity. If it still affects you, please add a comment to this issue with up-to-date information. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DanKaplanSES @aleks-pro