-
Notifications
You must be signed in to change notification settings - Fork 70
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
[8 0f #107] move base env tool providers to dedicated files #130
[8 0f #107] move base env tool providers to dedicated files #130
Conversation
/** | ||
* Steps to peform after the env is updated, and potentially reconfigured | ||
*/ | ||
postInstall?: ( |
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.
Cute :)
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.
?
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.
Haha nothing :)
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.
Thanks @bollwyvl for the awesome refactoring work!
LGTM :)
@goanpeca thanks for the quick review... think i hit all the points raised above... |
Not _quite_ready...
I want those slashes to be consistent... |
Looks better:
|
Ok, I think the log output is good now... added a final output, just so there's a timestamp outside the group. |
This moves extra tools for the
base
env into dedicated files, and finally reducessetup.ts
to right at 100 lines.This is the end of what #107 had implemented, and no additional changes are planned at this scale 🎉
Thanks @goanpeca for the review