-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(scope-manager): throws unhelpful aaa error message because analyze expects Program
#11747
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
base: main
Are you sure you want to change the base?
Conversation
|
Thanks for the PR, @nayounsang! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit 1282ebc
☁️ Nx Cloud last updated this comment at |
scope-manager throws unhelpful aaa error message because analyze expects Programaaa error message because analyze expects Program
aaa error message because analyze expects Programaaa error message because analyze expects Program
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #11747 +/- ##
=======================================
Coverage 90.66% 90.67%
=======================================
Files 518 518
Lines 52444 52447 +3
Branches 8690 8691 +1
=======================================
+ Hits 47548 47554 +6
+ Misses 4882 4879 -3
Partials 14 14
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|

PR Checklist
aaaerror message #11727Overview
aaaSince changed the type of
analyze, I'm wondering if it's correct to write the test as it is now.(I don't know if that makes sense!)And I'd like to know what happens when the range option isn't set. I'll leave it as a draft. I haven't been able to reproduce it yet.