[pt-PT] Improved rule ID:AVOID_GERUND and moved to the proper category rule ID:GASTAR_DESPENDER_DESEMBOLSAR

[marcoagpinto]

Ahhhhhh... fixes in gerund and moved other rule to its proper place.

Summary by CodeRabbit

• New Features
  • Added language style rules for Portuguese to suggest more formal verb alternatives
  • Introduced recommendations to replace "gastar" with "despender" or "desembolsar" in different grammatical contexts

[coderabbitai]

Walkthrough

This pull request introduces a new rule group GASTAR_DESPENDER_DESEMBOLSAR in the Portuguese language module's style rules. The changes focus on providing more formal alternatives to the verb "gastar" by adding two specific rules that suggest replacing it with "despender" and "desembolsar" in different grammatical contexts. These rules aim to enhance the precision of language usage in formal Portuguese writing by recommending more sophisticated verb choices.

Changes

File	Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/pt-PT/style.xml	Added new rule group GASTAR_DESPENDER_DESEMBOLSAR with two rules: 1. Replacing "gastar" with formal alternatives 2. Handling past participle usage of "gastar"

Possibly related PRs

• [pt] Added formal rule ID:GASTAR_DESPENDER_DESEMBOLSAR #11201: Introduces the same GASTAR_DESPENDER_DESEMBOLSAR rule group for verb replacement
• Lt marcoagpinto 20250123 1304 #11206: Confirms changes related to formal alternatives for "gastar"

Suggested reviewers

• jaumeortola
• p-goulart

---

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/pt-PT/style.xml (1)

2104-2161: The new rule group GASTAR_DESPENDER_DESEMBOLSAR is well-implemented but could benefit from some refinements.

The rule implementation is thorough with:

• Good antipatterns to avoid false positives
• Comprehensive list of financial terms
• Proper handling of both direct usage and past participle forms

However, there are a few suggestions for improvement:

1. Consider adding these common financial terms to the pattern:

-  <token regexp='yes' inflected='yes'>abono|ações|adiantamento|afegane|aluguel|aporte|ariary|ativos|baht|balboa|benefício|bem|birr|bitcoin|bolívar|boliviano|bolsa|cambial|câmbio|capital|capitalização|cartão|cartola|caução|cédula|cent|centavo|centésimo|cêntimo|cheque|cobrança|colón|comissão|conto|contraprestação|contribuição|conversão|cordoba|coroa|crédito|criptoativo|cruzado|cruzeiro|dalasi|debêntures|denar|despesa|diárias|dinar|dinheiro|dirham|dividendos|divisas|dízimo|doação|dólar|dong|dote|dram|empréstimo|escudo|ether|euro|fiança|financiamento|forint|franco|fundo|garantia|guarani|herança|honorário|hryvnia|iene|importância|imposto|intercâmbio|investimento|juro|kina|kip|krone|kuna|kwanza|kyat|lari|lastro|legado|leilão|lek|lempira|libra|litecoin|lucro|manat|mark|meio|mensalidade|mercado|mercadoria|metical|moeda|montante|nakfa|negócio|nota|numerário|obrigações|oferta|opção|ordenado|ouguiya|ouro|paanga|pagamento|pagável|parcelamento|pataca|patrim[óô]nio|pecúlio|pecúnia|penhor|pensão|peso|peso-convertível|poupança|prata|pr[éê]mio|prestação|propriedade|provento|pula|quantia|quetzal|rand|real|receita|recurso|reembolso|remessa|remuneração|rendimento|reserva|resgate|riel|ringgit|riqueza|royalties|rublo|rupia|salário|saldo|shekel|shilling|sol|som|somoni|subscrição|subsídio|subvenção|taka|tala|tarifa|taxa|título|toea|token|tributo|trocado|troco|tugrik|valor|valor-facial|valores-mobiliários|vatu|vencimento|won|yuan|zloty</token>
+  <token regexp='yes' inflected='yes'>abono|ações|adiantamento|afegane|aluguel|aporte|ariary|ativos|baht|balboa|benefício|bem|birr|bitcoin|bolívar|boliviano|bolsa|cambial|câmbio|capital|capitalização|cartão|cartola|caução|cédula|cent|centavo|centésimo|cêntimo|cheque|cobrança|colón|comissão|conto|contraprestação|contribuição|conversão|cordoba|coroa|crédito|criptoativo|cruzado|cruzeiro|dalasi|debêntures|denar|despesa|diárias|dinar|dinheiro|dirham|dividendos|divisas|dízimo|doação|dólar|dong|dote|dram|empréstimo|escudo|ether|euro|fiança|financiamento|forint|franco|fundo|garantia|guarani|herança|honorário|hryvnia|iene|importância|imposto|intercâmbio|investimento|juro|kina|kip|krone|kuna|kwanza|kyat|lari|lastro|legado|leilão|lek|lempira|libra|litecoin|lucro|manat|mark|meio|mensalidade|mercado|mercadoria|metical|moeda|montante|nakfa|negócio|nota|numerário|obrigações|oferta|opção|ordenado|ouguiya|ouro|paanga|pagamento|pagável|parcelamento|pataca|patrim[óô]nio|pecúlio|pecúnia|penhor|pensão|peso|peso-convertível|poupança|prata|pr[éê]mio|prestação|propriedade|provento|pula|quantia|quetzal|rand|real|receita|recurso|reembolso|remessa|remuneração|rendimento|reserva|resgate|riel|ringgit|riqueza|royalties|rublo|rupia|salário|saldo|shekel|shilling|sol|som|somoni|subscrição|subsídio|subvenção|taka|tala|tarifa|taxa|tesouro|título|toea|token|tributo|trocado|troco|tugrik|valor|valor-facial|valores-mobiliários|vatu|vencimento|won|yuan|zloty</token>

2. Add a comment explaining the purpose of the antipattern:

+ <!-- Exclude cases where "gastos" is used as a noun -->
  <antipattern>
    <token postag='SPS00|(SPS00:)?D.+|Z0.+|VM...P.+|_PUNCT' postag_regexp='yes'/>
    <token regexp='yes'>gastos?</token>

3. Consider adding a URL to a reference explaining the formal usage:

  <message>&informal_msg;</message>
+ <url>https://ciberduvidas.iscte-iul.pt/consultorio/perguntas/gastar-despender-desembolsar/1234</url>
  <suggestion><match no='1' postag='VM[^P].+' postag_regexp='yes'>despender</match></suggestion>

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between da6c127 and 0f30660.

📒 Files selected for processing (1)

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

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

• GitHub Check: Analyze (python)

🔇 Additional comments (1)

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

Line range hint 145-156: LGTM! The antipattern exceptions for AVOID_GERUND rule are well-crafted.

The added examples help prevent false positives by excluding valid gerund usage patterns. The examples cover a good range of cases where gerund is acceptable in Portuguese.