Skip to content

Explain usage of monitor --config in command help #2249

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

Merged
merged 1 commit into from
Jul 24, 2023
Merged

Explain usage of monitor --config in command help #2249

merged 1 commit into from
Jul 24, 2023

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Jul 23, 2023

Please check if the PR fulfills these requirements

See how to contribute

  • The PR has no duplicates (please search among the Pull Requests
    before creating one)
  • The PR follows
    our contributing guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • UPGRADING.md has been updated with a migration guide (for breaking changes)
  • configuration.schema.json updated if new parameters are added.

What kind of change does this PR introduce?

docs update

What is the current behavior?

The --config flag of the arduino-cli monitor command is used to configure the communication port used by the monitor.

Previously the command line help did not provide any guidance for the usage of this flag, which might lead the users to wonder (#2070):

  • How can the configuration options available for use via the flag be determined?
  • What is the format for the configuration option argument?

The information is provided in the FAQ page of the documentation (#2247), but that is not as convenient a source of information as the command line help and the user may not even be aware of its existence.

What is the new behavior?

Adjust the command help to provide the user with the missing information by:

  • Creating a conceptual linkage between the --config and --describe flags by using the "communication port settings" terminology in the references of both.
  • Documenting the argument format.

In addition to the comma-separated list format I documented here, an alternative usage of passing multiple --config flags is also supported. I chose the former because I felt that the descriptions of the latter in either command line notation (e.g., [--config <ID>=<value>]...) or in prose (e.g., "The format is <ID>=<value>. Can be used multiple times for multiple settings.") were less clear.

Does this PR introduce a breaking change, and is titled accordingly?

No breaking change.

The `--config` flag of the `arduino-cli monitor` command is used to configure the communication port used by the
monitor.

Previously the command line help did not provide any guidance for the usage of this flag, which might lead the users to
wonder:

- How can the configuration options available for use via the flag be determined?
- What is the format for the configuration option argument?

The information is provided in the FAQ page of the documentation, but that is not as convenient a source of information
as the command line help and the user may not even be aware of its existence.

The command help is hereby adjusted to provide the user with this information:

- Create a conceptual linkage between the `--config` and `--describe` flags by using the "communication port settings"
  terminology in the references of both.
- Document the argument format.

In addition to the comma-separated list format I documented here, an alternative usage of passing multiple `--config`
flags is also supported. I chose the former because I felt that the descriptions of the latter in either command line
notation (e.g., `[--config <ID>=<value>]...`) or in prose (e.g., "The format is <ID>=<value>. Can be used multiple times
for multiple settings.") were less clear.
@per1234 per1234 added type: enhancement Proposed improvement topic: documentation Related to documentation for the project labels Jul 23, 2023
@per1234 per1234 requested a review from MatteoPologruto July 23, 2023 21:19
@per1234 per1234 self-assigned this Jul 23, 2023
@per1234
Copy link
Contributor Author

per1234 commented Jul 24, 2023

The failing tests in the "Test Go" workflow run is unrelated to the changes proposed here and also occurs on the master branch:

https://github.com/arduino/arduino-cli/actions/runs/5641529705/job/15279738546#step:6:13559

Copy link
Contributor

@MatteoPologruto MatteoPologruto left a comment

Choose a reason for hiding this comment

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

Thanks Per! I'm fixing the tests in a different PR.

@per1234 per1234 merged commit 78d19fa into arduino:master Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: documentation Related to documentation for the project type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants