Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pt] Added formal rule ID:GASTAR_DESPENDER_DESEMBOLSAR #11201

Merged
merged 1 commit into from
Jan 20, 2025

Conversation

marcoagpinto
Copy link
Member

@marcoagpinto marcoagpinto commented Jan 20, 2025

Ahhhh… I feel really great with this new rule.

Summary by CodeRabbit

  • New Features
    • Enhanced Portuguese language grammar checking with new style rules
    • Added rules to suggest more formal alternatives for the verb "gastar"
    • Improved language tool's grammatical suggestion capabilities for verb usage

Copy link
Contributor

coderabbitai bot commented Jan 20, 2025

Walkthrough

A new rule group GASTAR_DESPENDER_DESEMBOLSAR has been added to the Portuguese language module's style rules. The addition includes two rules focusing on the correct usage of the verb "gastar" (to spend). These rules aim to improve grammatical suggestions by identifying and providing alternatives for improper uses of the verb, particularly its past participle forms. The rules are designed to suggest more formal alternatives like "despender" or "desembolsar" in specific linguistic contexts.

Changes

File Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/style.xml - Added new rule group GASTAR_DESPENDER_DESEMBOLSAR
- Introduced two new rules targeting incorrect usage of "gastar"
- Rules include antipatterns and suggestions for more formal verb alternatives

Possibly related PRs

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
🪧 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/style.xml (3)

4118-4120: Consider removing or reformatting the ChatGPT comment.

While it's good to acknowledge external tools, inline comments about AI usage might not be suitable for production code. Consider moving this information to the PR description or commit message instead.


4139-4139: Consider adding more modern currency terms.

The financial terms list is comprehensive but could benefit from adding more modern terms like:

  • Popular cryptocurrencies (e.g., "cardano", "dogecoin", "solana")
  • Digital payment terms (e.g., "stablecoin", "wallet", "nft")

Also applies to: 4164-4164


4169-4171: Add more complex test examples.

The current examples are good but basic. Consider adding more complex cases to verify the rule's behavior:

  • Multiple auxiliary verbs (e.g., "tinha estado gasto")
  • Negations (e.g., "não tinha gasto")
  • Interrupted patterns (e.g., "tinha realmente gasto")
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 781de04 and 0613e1d.

📒 Files selected for processing (1)
  • languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/style.xml (1 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)

4136-4137: Review the token skip distance.

The skip='4' attribute allows up to 4 words between tokens, which might be too permissive and could lead to false positives. Consider reducing this value or adding more specific constraints to prevent incorrect matches.


4118-4172: Verify integration with existing rules.

Let's check for similar rules in other languages and potential conflicts:

✅ Verification successful

Rule integration verified successfully.

The "gastar → despender/desembolsar" rule is properly integrated with existing rules in the Portuguese language module, with no conflicts found. The implementation includes comprehensive antipatterns and follows the established pattern structure.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for similar rules in other language modules
echo "Searching for similar rules in other language modules..."
find . -name "style.xml" -not -path "*pt/*" -exec grep -l "gastar\|despender\|desembolsar" {} \;

# Check for potential rule conflicts in Portuguese module
echo "Checking for potential rule conflicts..."
rg -A 5 "gastar|despender|desembolsar" "languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/"

Length of output: 18014

@marcoagpinto marcoagpinto merged commit 0e15748 into master Jan 20, 2025
5 checks passed
@marcoagpinto marcoagpinto deleted the lt_marcoagpinto_20250120_1940 branch January 20, 2025 20:11
@susanaboatto
Copy link
Collaborator

Hi @marcoagpinto!

I think this fits better in the pt-PT file only. Would you mind moving it there?

Thank you :D

@marcoagpinto
Copy link
Member Author

Hi @marcoagpinto!

I think this fits better in the pt-PT file only. Would you mind moving it there?

Thank you :D

Sure. Thanks for the feedback.

Give me a few minutes.

😛 😛 😛 😛

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants