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

[no-internal-report] allow passing custom tsconfig path, and fail verbosely if tsconfig.json isn't found #44

Open
MichaelBelousov opened this issue Aug 2, 2023 · 0 comments
Open

[no-internal-report] allow passing custom tsconfig path, and fail verbosely if tsconfig.json isn't found #44

MichaelBelousov opened this issue Aug 2, 2023 · 0 comments
Labels
good first issue Good for newcomers

Comments

@MichaelBelousov
Copy link
Contributor

The current no-internal-report logic assumes tsconfig.json is defined. It isn't always, some people use different names so we should allow specifying it
@MichaelBelousov MichaelBelousov added the good first issue Good for newcomers label Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MichaelBelousov