Skip to content

Conversation

@waldyrious
Copy link
Member

@waldyrious waldyrious commented Dec 6, 2025

Scamper's documentation explicitly refers to "warts" as a file format.

Using the .warts form in the command descriptions, instead of just warts, makes this more explicit and intuitive.

Checklist

  • The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
  • The page description(s) have links to documentation or a homepage.
  • The page(s) follow the content guidelines.
  • The page(s) follow the style guide.
  • The PR contains at most 5 new pages.
  • The PR is authored by me, or has been human-reviewed if it was created with AI or machine translation software.
  • The PR title conforms to the recommended templates.
  • Version of the command being documented (if known):
  • Reference issue: #

@github-actions github-actions bot added mass changes Changes that affect multiple pages. page edit Changes to an existing page(s). review needed Prioritized PRs marked for reviews from maintainers. labels Dec 6, 2025
@Managor
Copy link
Member

Managor commented Dec 6, 2025

🤔
This could be standardized in the style guide.

@waldyrious
Copy link
Member Author

This could be standardized in the style guide.

Honestly, I was checking the style guide and it feels like it's quite bloated already 😅 I'm hesitant to add yet another guideline for something that in practice isn't a super common issue (nor, admittedly, that problematic anyway).

@Managor
Copy link
Member

Managor commented Dec 6, 2025

The hesitation goes away when you consider the style guide less as a bible, but a collection of best practices. This feels very similar to environment variable change in #19685

@waldyrious
Copy link
Member Author

This could be standardized in the style guide.

For future reference, this was proposed in #19776.

@Managor Managor merged commit ef4d4cb into main Dec 9, 2025
10 checks passed
@Managor Managor deleted the warts branch December 9, 2025 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mass changes Changes that affect multiple pages. page edit Changes to an existing page(s). review needed Prioritized PRs marked for reviews from maintainers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants