Skip to content

[skip changelog] Correct documentation re: default for build_cache.path configuration key #2919

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
May 28, 2025

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented May 26, 2025

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
  • [N/A] Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • [N/A] UPGRADING.md has been updated with a migration guide (for breaking changes)
  • [N/A] configuration.schema.json updated if new parameters are added.

What kind of change does this PR introduce?

Docs fix

What is the current behavior?

The "Configuration" documentation page includes information on the default values of the configuration keys.

The default value of the build_cache.path configuration key was recently changed (#2673), but the documentation was not updated accordingly so it provides incorrect information regarding the default build cache location.

What is the new behavior?

The documentation is updated to provide the correct information regarding the default value of the build_cache.path configuration key.

Previously, the information was provided in the list of keys. That is a non-standard location for the information as there is an established convention of instead providing this information in the separate section of the page dedicated to documenting default paths. In addition. the location in the keys list became more problematic for the new default since it is operating system-specific and thus the increased volume of documentation content would be awkward to fit into the nested list of keys. For these reasons, the documentation content was moved to the standardized location under the "Default directories" section of the page.

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

No breaking change.

…ath` configuration key

The "Configuration" documentation page includes information on the default values of the configuration keys.

The default value of the build_cache.path configuration key was recently changed, but the documentation was not updated
accordingly.

The documentation is hereby updated to provide the correct information regarding the default value of the
build_cache.path configuration key.

Previously, the information was provided in the list of keys. That is a non-standard location for the information as
there is an established convention of instead providing this information in the separate section of the page dedicated
to documenting default paths. In addition. the location in the keys list became more problematic for the new default
since it is operating system-specific and thus the increased volume of documentation content would be awkward to fit
into the nested list of keys. For these reasons, the documentation content was moved to the standardized location under
the "Default directories" section of the page.
@per1234 per1234 requested a review from cmaglie May 26, 2025 09:41
@per1234 per1234 self-assigned this May 26, 2025
@per1234 per1234 added topic: documentation Related to documentation for the project type: imperfection Perceived defect in any part of project labels May 26, 2025
@per1234 per1234 merged commit 55f86b5 into arduino:master May 28, 2025
6 checks passed
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: imperfection Perceived defect in any part of project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants