Skip to content

Comments

fix: improve consistency of backticks in usage messages#863

Merged
dandavison merged 1 commit intotemporalio:mainfrom
stpierre:audit-backticks
Nov 13, 2025
Merged

fix: improve consistency of backticks in usage messages#863
dandavison merged 1 commit intotemporalio:mainfrom
stpierre:audit-backticks

Conversation

@stpierre
Copy link
Member

What was changed

  • Remove extraneous trailing backticks
  • Add missing backticks where obviously needed
  • Improve consistency of quoting

This doesn't fix every inconsistent use of backticks, but it does remove a few dangling backticks, and in places where quoting was inconsistent (i.e., a mix of backticks, quotes, and/or no quotes in a single usage message) makes it slightly more consistent.

Why?

Prettier usage :)

Checklist

  1. Closes

  2. How was this tested:

  1. Any docs updates needed?

@stpierre stpierre requested review from a team as code owners October 10, 2025 18:06
@CLAassistant
Copy link

CLAassistant commented Oct 10, 2025

CLA assistant check
All committers have signed the CLA.

s.Command.Short = "Show Workflow Executions"
if hasHighlighting {
s.Command.Long = "List Workflow Executions. The optional \x1b[1m--query\x1b[0m limits the output to\nWorkflows matching a Query:\n\n\x1b[1mtemporal workflow list \\\n --query YourQuery\x1b[1m\x1b[0m\n\nVisit https://docs.temporal.io/visibility to read more about Search Attributes\nand Query creation. See \x1b[0mtemporal batch --help` for a quick reference.\n\nView a list of archived Workflow Executions:\n\n\x1b[1mtemporal workflow list \\\n --archived\x1b[0m"
s.Command.Long = "List Workflow Executions. The optional \x1b[1m--query\x1b[0m limits the output to\nWorkflows matching a Query:\n\n\x1b[1mtemporal workflow list \\\n --query YourQuery\x1b[0m\n\nVisit https://docs.temporal.io/visibility to read more about Search Attributes\nand Query creation. See \x1b[1mtemporal batch --help\x1b[0m for a quick reference.\n\nView a list of archived Workflow Executions:\n\n\x1b[1mtemporal workflow list \\\n --archived\x1b[0m"
Copy link
Contributor

Choose a reason for hiding this comment

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

Anyone know why the ANSI escapes changed here? Haven't tested in a terminal but the new version LGTM. (1m is a transition to bold and 0m is a transition that removes all flags.)

Copy link
Member Author

Choose a reason for hiding this comment

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

I believe this is related to this change; previously there was an extraneous hanging backtick on the code block for temporal workflow list --query YourQuery, so the parser that creates the highlighted version of the help text may have gotten a bit confused. Here's how it looks today:

image

With this patch:

image

This is actually the exact typo that I noticed that sent me down this rabbit hole 😄

Copy link
Contributor

Choose a reason for hiding this comment

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

Excellent, thanks for looking into this.

Copy link
Contributor

@dandavison dandavison left a comment

Choose a reason for hiding this comment

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

Thanks @stpierre! LGTM

* Remove extraneous trailing backticks
* Add missing backticks where obviously needed
* Improve consistency of quoting

This doesn't fix every inconsistent use of backticks, but it does remove a few dangling backticks, and in places where quoting was inconsistent (i.e., a mix of backticks, quotes, and/or no quotes in a single usage message) makes it slightly more consistent.
@dandavison dandavison merged commit 1b9b20c into temporalio:main Nov 13, 2025
8 checks passed
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.

4 participants