[pt-PT] Rewrote rule ID:CHEGAR_AO_FIM_FINDAR_TERMINAR

[marcoagpinto]

Rewrote the rule.

It has become a lot more powerful.

Summary by CodeRabbit

• New Features
  • Introduced new language rules for improving clarity and formality in written Portuguese.
  • Added rules to address common linguistic issues and promote precise language usage.
  • Enhanced suggestions for replacing informal expressions with more formal alternatives.
  • Expanded rules on redundancy and pleonasms to include more examples and simplifications.

[coderabbitai]

Walkthrough

The pull request introduces significant modifications to the style.xml file for Portuguese (Portugal) language rules in LanguageTool. It encompasses the addition, modification, and removal of numerous rules and patterns designed to enhance linguistic accuracy and formality. New rules target specific language issues, while existing rules are refined to provide clearer formal alternatives. The overall structure of the XML remains intact, with an emphasis on promoting precision in written Portuguese.

Changes

File	Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/pt-PT/style.xml	Extensive additions of rules and rule groups aimed at improving language clarity and formality, including rules addressing common linguistic issues, redundancy, and informal expressions.

Possibly related PRs

• [pt-PT] Fixed FPs in rule ID:VERBO_PRONOMINAL_DE_V3 #10907: Modifies the same style.xml file, adding rules for "caixa" and "embalagem" confusion and using "gosto" instead of "prazer."
• [pt-PT] Improved rule ID:CONFUSÃO_CAIXA_EMBALAGEM and cleaned other rule #10932: Improves the CONFUSÃO_CAIXA_EMBALAGEM and PRAZER_GOSTO rules, directly related to the main PR's changes.
• [pt-PT] Removed "temp_off" from rules #10935: Removes the temp_off designation from the CONFUSÃO_CAIXA_EMBALAGEM rule, indicating a direct connection to the main PR.
• [pt-PT] Better suggestion and moved to formal category ID:FAZER_DESPORTO #10948: Introduces the FAZER_DESPORTO rule, suggesting "praticar" instead of "fazer desporto," aligning with the main PR's formal language focus.
• [pt-PT] Rewrote rule ID:CONCLUIR_UM_CURSO #10940: Rewrites the CONCLUIR_UM_CURSO rule, relevant to formal language usage in academic contexts.
• [pt-PT] Improved rule ID:AVIÃO_DE_COMBATE_PT_PT (regexp+suggestion) #10949: Adds rules enhancing clarity and formality, similar to the objectives of the main PR.

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 (1)

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

4110-4138: Improvements to the 'CHEGAR_AO_FIM_FINDAR_TERMINAR' rule look good, but consider activating it.

The changes to this rule, including the addition of antipatterns and refinement of the main pattern, appear to enhance its effectiveness in simplifying the phrase "chegar ao fim" to more concise alternatives. However, the rule is currently set to "temp_off".

Consider removing the default="temp_off" attribute if this improved version is ready for active use.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 055bbe6 and 37b2587.

📒 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