-
Notifications
You must be signed in to change notification settings - Fork 344
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
fix: Don't log info about the built extension when signing #577
Conversation
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 tested this out and it works great, thanks! I made a small request to fix some formatting.
Generally for patches like this we would need a test that ensures the run
command is calling build()
in a way that will execute the desired behavior. However, it's just a log statement in this case which is a bit harder to test so it's ok.
@@ -69,7 +69,8 @@ export default function sign( | |||
} | |||
|
|||
let [buildResult, idFromSourceDir] = await Promise.all([ | |||
build({sourceDir, artifactsDir: tmpDir.path()}, {manifestData}), | |||
build({sourceDir, artifactsDir: tmpDir.path()}, {manifestData, | |||
showReadyMessage: false}), |
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.
nitpicky request (sorry): when breaking a block into a new line, the break needs to be consistent. In this case the block is {manifestData, showReadyMessage: false}
. You could make it break consistently in a couple different ways:
Here is an example of keeping all block elements on the same line:
build({sourceDir, artifactsDir: tmpDir.path()}, {
manifestData, showReadyMessage: false,
}),
Here is an example of moving the entire block to a new line:
build({sourceDir, artifactsDir: tmpDir.path()},
{manifestData, showReadyMessage: false}),
This type of consistency is hard to enforce with automatic lint rules so sorry about slowing you down to fix that. It's important to fix these kinds of things because otherwise other contributors may become distracted by the inconsistency when working on an unrelated feature.
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.
@kumar303 no problem, good to learn the something new
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.
Sorry, one more nitpick. I'll try and see if I can add a lint rule to catch these :)
@@ -78,7 +79,8 @@ export type PackageCreatorFn = | |||
(params: PackageCreatorParams) => Promise<ExtensionBuildResult>; | |||
|
|||
async function defaultPackageCreator( | |||
{manifestData, sourceDir, fileFilter, artifactsDir}: PackageCreatorParams | |||
{manifestData, sourceDir, fileFilter, artifactsDir, | |||
showReadyMessage}: PackageCreatorParams |
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.
oops, I completely missed this one. This is also formatted inconsistently because the block is only partially broken into the next line. An easy fix would be:
async function defaultPackageCreator({
manifestData, sourceDir, fileFilter, artifactsDir, showReadyMessage
}: PackageCreatorParams): Promise<ExtensionBuildResult> {
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.
no worries, let me know if you see anything else
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!
Fix #181
Manually tested with example addon