-
Notifications
You must be signed in to change notification settings - Fork 573
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
Upgrade to oclif 4.x #5130
Upgrade to oclif 4.x #5130
Conversation
.run() | ||
.then(require('@oclif/core/flush')) | ||
.catch(require('@oclif/core/handle')) | ||
require('@oclif/core').execute({ dir: __dirname }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change makes me a little nervous, but is the new? default according to the docs. Doing it the way we had was making it throw stack traces for even non-error things which was very strange.
@@ -19,7 +19,7 @@ export class BannedCommand extends IronfishCommand { | |||
sort: { | |||
...sort, | |||
exclusive: ['follow'], | |||
}, | |||
} as typeof sort, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:(
I don't know why it started complaining about the type inference here, but here we are. There might some Typescript-ism that does what it wants here without the as
keyword, but I don't have any clever ideas right now and this does the job
It looks like we were using this library which we had because it was being installed as an indirect dependency. That indirect dependency has apparently been removed, which was causing our usage of it to break.
Summary
The final oclif 4.x upgrade PR
Testing Plan
Documentation
N/A
Breaking Change
N/A