On app selection keep retrying when failing but avoid capturing unrelated errors#6904
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Coverage report
Test suite run success3788 tests passing in 1448 suites. Report generated by 🧪jest coverage report action from f3d32ce |
f35bc45 to
47e6658
Compare
|
We detected some changes at Caution DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release. |
|
🤖 Code Review · #projects-dev-ai for questions ✅ Complete - No issues 📋 History✅ 2 findings → ✅ No issues → ✅ No issues → ✅ No issues → ✅ No issues → ✅ No issues |
isaacroldan
left a comment
There was a problem hiding this comment.
Let's remove the ! and handle the undefined selected app outside
47e6658 to
d1c840f
Compare
ee4e139 to
d914c87
Compare
d914c87 to
f3d32ce
Compare

WHY are these changes introduced?
Vault Error
GH Issue #15725
Observe link
The app selection logic contained redundant error handling and retry mechanisms that were making the code unnecessarily complex and potentially masking actual issues during the selection process.
WHAT is this pull request doing?
selectAppPromptfunction that was checking for null after using the non-null assertion operatorselectOrCreateAppby removing try-catch blocks and letting natural control flow handle retriesHow to test your changes?
shopify app devin a project directoryMeasuring impact
How do we know this change was effective? Please choose one:
Checklist