feat: migrate static examples to use color.command() - part 2 #3490
+229
−200
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR is the second batch of the migration to use semantic
color.command()for CLI command examples in static example/examples properties. This continues the work from the color system migration from@heroku-cli/colorto@heroku/heroku-cli-util.Updates 29 command files to wrap CLI command examples with
color.command()using template literals, enabling semantic coloring of command examples in help text.Changes
exampleandexamplesproperties to use${color.command('...')}pattern@heroku-cli/colorto@heroku/heroku-cli-utilwhere neededcolorimports to files that were missing themcerts/update.tsandpg/connection-pooling/attach.tsType of Change
Feature Additions (minor semver update)
Testing
Notes:
This change affects how command examples are displayed in help text, using semantic color functions instead of direct strings.
Steps:
color.command()functionRelated Issues
follow-on from #3488
https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00002T2hvTYAR/view