[pt] Removed "temp_off" from two rules

[marcoagpinto]

Removed "temp_off".

Summary by CodeRabbit

• Style
  • Removed default='temp_off' attribute from two language rule configurations in Portuguese language module
  • Potentially activates previously disabled style rules for language processing

[coderabbitai]

Walkthrough

The pull request modifies the style.xml configuration file for Portuguese language rules in LanguageTool. Specifically, it removes the default='temp_off' attribute from two XML elements: a rule group with the ID GASTAR_DESPENDER_DESEMBOLSAR and a rule with the ID QUE_VEM_PROXIMA. This change alters the default activation state of these language processing rules, potentially enabling them to be active by default instead of being temporarily disabled.

Changes

File	Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/style.xml	- Removed default='temp_off' from <rulegroup id='GASTAR_DESPENDER_DESEMBOLSAR'> - Removed default='temp_off' from <rule id='QUE_VEM_PROXIMA'>

Possibly related PRs

• [pt] Removed "temp_off" from rule ID:OS_DOIS_AS_DUAS_AMBOS_AMBAS #10870: Removes default='temp_off' from rule group OS_DOIS_AS_DUAS_AMBOS_AMBAS
• [pt] Removed "temp_off" from rule ID:OS_DOIS_AS_DUAS_AMBOS_AMBAS #10887: Modifies the same rule group OS_DOIS_AS_DUAS_AMBOS_AMBAS
• [pt-PT] Removed "temp_off" from subrule in ID:INFORMALITIES #10885: Removes temp_off designation from a subrule in the INFORMALITIES group

Suggested reviewers

• jaumeortola

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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

🧹 Nitpick comments (1)

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

4118-4118: Consider adding a changelog entry for enabling these style rules.

Since you're enabling two previously disabled style rules that affect formal writing suggestions, it would be helpful to:

1. Add a changelog entry explaining why these rules are now considered stable enough for default activation
2. Document any known limitations or specific use cases where these rules are most beneficial

Also applies to: 4287-4287

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0ef487f and 6dd1301.

📒 Files selected for processing (1)

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

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (python)
• GitHub Check: Analyze (java-kotlin)

🔇 Additional comments (2)

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

4118-4118: Verify testing coverage before enabling the rule by default.

The removal of default='temp_off' will activate this formal language suggestion rule by default. Since this is a style rule suggesting formal alternatives for "gastar", please ensure it has been thoroughly tested to avoid false positives in contexts where "gastar" is appropriate.

Run this script to check for any related test cases:

---

4287-4287: Document the rationale for enabling the simplification rule.

The removal of default='temp_off' will activate this simplification rule by default. While simplifying "Substantivo + que vem" to "próxim(ao)(s) + substantivo" can improve readability, please:

1. Ensure thorough testing to avoid false positives
2. Consider documenting why these rules are now being enabled by default

Run this script to check for any related test cases and reported issues: