-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
cleanup(react): improved error message throwed when executor is not available or not valid #23282
Conversation
…vailable or not valid The error message which is throwed when executer is not available or not valid is really confusing. Hence updating it to throw the exact issue why it errored
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit bab82d5. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
…vailable or not valid (#23282) The error message which is throwed when executer is not available or not valid is really confusing. Hence updating it to throw the exact issue why it errored. <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> ## Current Behavior The error message throwed is really vauge. And does't really tell anything about why it happened. Fixes # Improved error message which is throwed when excuter is not valid or not present in the project.json <img width="1421" alt="Screenshot 2024-05-10 at 1 17 05 AM" src="https://github.com/nrwl/nx/assets/54993680/455163e4-3197-419c-b511-040c35784a72"> (cherry picked from commit eb44f9b)
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
The error message which is throwed when executer is not available or not valid is really confusing. Hence updating it to throw the exact issue why it errored.
Current Behavior
The error message throwed is really vauge. And does't really tell anything about why it happened.
Fixes #
Improved error message which is throwed when excuter is not valid or not present in the project.json