[pt-PT] Better suggestion and moved to formal category ID:FAZER_DESPORTO

[marcoagpinto]

Better suggestion, extra example and better regexp.

Summary by CodeRabbit

• New Features

  • Introduced a new rule to suggest replacing "fazer desporto" with the more formal "praticar desporto" in Portuguese.
  • Added clarification on the usage of formal language in sports terminology with examples.

• Bug Fixes

  • Removed the previously commented-out rule for "fazer desporto," streamlining the approach to language suggestions.

[coderabbitai]

Walkthrough

The changes in this pull request introduce a new rule in the Portuguese language module of LanguageTool, specifically within the style.xml file. The rule, FAZER_DESPORTO, replaces the informal expression "fazer desporto" with the more formal "praticar desporto." It includes a defined pattern for identifying instances of the informal phrase and suggests the formal alternative. Additionally, a previously commented-out version of the same rule has been removed, reflecting a shift towards promoting formal language usage in Portuguese.

Changes

File	Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/pt-PT/style.xml	Added rule FAZER_DESPORTO to replace "fazer desporto" with "praticar desporto"; removed commented-out rule.

Possibly related PRs

• [pt-PT] Added colloquialism rule to rulegroup ID:INFORMALITIES #10911: Modifies the FAZER_DESPORTO rule, directly related to the addition in this PR.
• [pt-PT] Fixed FPs in rule ID:VERBO_PRONOMINAL_DE_V3 #10907: Adds the FAZER_DESPORTO rule, aligning with the focus on formalizing the expression.
• [pt-PT] Removed "temp_off" from rules #10935: Activates the FAZER_DESPORTO rule by removing the temp_off designation.
• [pt-PT] Better suggestion in rule ID:CICLO_VICIOSO #10934: Improves the suggestion for the CICLO_VICIOSO rule, part of the broader effort to enhance formal language rules.

Suggested reviewers

• p-goulart
• susanaboatto

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)

languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/pt-PT/style.xml (2)

Line range hint 4-4: TODO: Add tests for this function.

It's important to implement unit tests for this function to ensure its correctness and prevent future regressions.

Would you like me to provide a sample unit test for this function?

---

Line range hint 1-24: Overall file review: Needs improvement in documentation and consistency.

1. Add a module-level docstring explaining the purpose of this file and its functions.
2. Ensure consistent coding style throughout (e.g., indentation, naming conventions).
3. Implement unit tests for all functions, as indicated by the TODO comment.
4. Review and update all function names to accurately reflect their behavior.
5. Consider adding type hints to function parameters and return values for better clarity.

These improvements will enhance the overall quality, maintainability, and readability of the code.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 7e3492f and 0fc6dae.

📒 Files selected for processing (1)

• languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/pt-PT/style.xml (1 hunks)

🧰 Additional context used