Skip to content
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

feat: display replacements on push/deploy #628

Merged
merged 6 commits into from
Nov 1, 2022

Conversation

mshanemc
Copy link
Contributor

@mshanemc mshanemc commented Oct 28, 2022

requires forcedotcom/source-deploy-retrieve#752

What does this PR do?

display for humans and json for replacements on push/deploy

What issues does this PR fix or reference?

@W-11949818@

@@ -117,6 +122,22 @@ export class DeployResultFormatter extends ResultFormatter {
return get(this.result, 'response', {}) as MetadataApiDeployStatus;
}

protected displayReplacements(): void {
if (this.isVerbose() && this.result.replacements?.size) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

only displaying replacements with --verbose? Same comment for pushResultFormatter below too

I would expect if there were any replacements, they'd be displayed without needing another flag?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for deploy, I could go either way. It felt noisy, like a thing I wouldn't want / pay attention to unless something weird was happening and I needed to investigate.

for push, they'll be there by default because it already has a quiet mode which omits them (from human and json). Or at least that's what I meant.

@WillieRuemmele WillieRuemmele merged commit 6fd2045 into main Nov 1, 2022
@WillieRuemmele WillieRuemmele deleted the sm/replacements-output branch November 1, 2022 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants