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
Modern logs for standalone
-specific commands
#10034
Conversation
Codecov Report
@@ Coverage Diff @@
## master #10034 +/- ##
==========================================
- Coverage 85.88% 85.70% -0.19%
==========================================
Files 333 333
Lines 13416 13434 +18
==========================================
- Hits 11523 11514 -9
- Misses 1893 1920 +27
Continue to review full report at Codecov.
|
lib/plugins/standalone.js
Outdated
const tagName = await standaloneUtils.resolveLatestTag(); | ||
const latestVersion = tagName.slice(1); | ||
if (latestVersion === currentVersion) { | ||
this.serverless.cli.log('Already at latest version'); | ||
const message = 'Already at latest version'; |
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 wouldn't introduce those variables, as when we will remove the legacy
calls, they will leave unnecessary verbosity.
I think it's fine in this case to keep given messages mentioned twice, it'll pay off in v3 branch
3d98b74
to
9e45fd2
Compare
lib/plugins/standalone.js
Outdated
@@ -40,10 +42,17 @@ module.exports = class Standalone { | |||
} | |||
|
|||
async upgrade() { | |||
const commandRunStartTime = Date.now(); |
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 think we can rely on pluginManager.commandRunStartTime
(?)
9e45fd2
to
6e865e7
Compare
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.
Looks great 👍
Addresses: #9860