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 APs to rule ID:GENERAL_NUMBER_AGREEMENT_ERRORS #11034

Merged
merged 1 commit into from
Nov 19, 2024

Conversation

marcoagpinto
Copy link
Member

@marcoagpinto marcoagpinto commented Nov 19, 2024

Just a couple of antipatterns.

Summary by CodeRabbit

  • New Features
    • Introduced two new antipatterns to enhance Portuguese grammar rules.
      • Added support for the idiomatic expression "fazer das tripas coração."
      • Implemented a complex token pattern for "d[oe]|no" with various contextual examples.

Copy link
Contributor

coderabbitai bot commented Nov 19, 2024

Walkthrough

The pull request introduces two new antipatterns to the Portuguese grammar rules in the grammar.xml file. One antipattern pertains to the idiomatic expression "fazer das tripas coração," detailing specific tokens and usage examples. The second antipattern involves a complex token pattern using regular expressions for "d[oe]|no," also accompanied by various contextual examples. These changes aim to enhance the language tool's grammar rules for Portuguese by expanding its coverage of idiomatic expressions and token patterns.

Changes

File Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/grammar.xml Added two antipatterns: one for the idiomatic expression "fazer das tripas coração" and another for the token pattern "d[oe]

Possibly related PRs

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

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

🧹 Outside diff range and nitpick comments (2)
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/grammar.xml (2)

4334-4343: LGTM! Consider adding a brief explanation of the idiom's meaning.

The antipattern correctly handles the Portuguese idiomatic expression "fazer das tripas coração" with proper token configuration and comprehensive examples covering various conjugations.

Consider adding a comment explaining the meaning of this idiom (e.g., "to make a supreme effort") to help non-Portuguese speakers maintain the code.


4333-4334: Improve comment documentation style.

While the comment correctly indicates these are global antipatterns, consider:

  1. Removing personal attribution from the comment
  2. Adding more context about why these patterns need global scope

Suggested comment style:

-           <!--
-           MARCOAGPINTO inserted global antipatterns for all subrules on top using the logic (2-MAR-2023+)
-      -->
+           <!-- Global antipatterns applied to all subrules
+                These patterns handle common exceptions to number agreement rules:
+                - Idiomatic expressions
+                - Language reference constructions
+           -->
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 8cb5fbb and 6156b5c.

📒 Files selected for processing (1)
  • languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/grammar.xml (1 hunks)
🔇 Additional comments (1)
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/grammar.xml (1)

4344-4353: Verify POS tag coverage for language names and consider expanding examples.

The antipattern effectively handles parenthetical language references with good flexibility in its token patterns. However:

  1. The POS tag pattern AQ.M[SN].+|N.M[SN].+ might need verification for complete coverage of language names.
  2. The examples focus only on English references.

Let's verify the coverage:

Consider adding examples with:

  • Other languages (e.g., "do francês", "do alemão")
  • Feminine language names (e.g., "da língua inglesa")
  • Different preposition combinations
✅ Verification successful

Let me analyze the search results to verify the POS tag coverage and language references.

The search results show that the codebase has extensive support for language references across multiple language modules (pt, en, es, fr, etc.) with various POS tag patterns. Looking at the examples in the Portuguese rules, I found evidence of similar parenthetical language references:

  1. (do inglês codecs)
  2. (do inglês "codecs")
  3. (do inglês Beats per minute, que significa Batidas por minuto)

Let me verify the POS tag coverage with a more specific search:


Based on the search results, I can now generate the final response:

POS tag coverage is appropriate and examples are well-balanced

The antipattern effectively handles language references with:

  1. Correct POS tag pattern AQ.M[SN].+|N.M[SN].+ covering both adjectives and nouns in masculine singular/plural forms
  2. Diverse examples found in the codebase:
    • Technical terms: (do inglês codecs)
    • Longer explanations: (do inglês Beats per minute, que significa Batidas por minuto)
    • Optional quotation marks: (do inglês "codecs")
    • Other references: (do Pai Natal)
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for potential language reference patterns that might be missed
# Look for similar language reference patterns in the codebase

# Search for parenthetical language references
rg -i '\([^)]*(?:do|da|no)\s+[^)]+\)' --type xml

# Search for language names with different POS tags
ast-grep --pattern '<token postag="$_" postag_regexp="yes">$_</token>'

Length of output: 62338


Script:

#!/bin/bash
# Search for language name POS tag patterns in Portuguese rules
rg -A 2 'postag="[AN]Q\.M[SN]\.+\|N\.M[SN]\.+"' --type xml languagetool-language-modules/pt/

# Search for other language reference examples
rg -B 1 -A 1 '\(do \w+ .*?\)' --type xml languagetool-language-modules/pt/

Length of output: 2343

@marcoagpinto marcoagpinto merged commit 8b6f874 into master Nov 19, 2024
5 checks passed
@marcoagpinto marcoagpinto deleted the lt_marcoagpinto_20241119_0814 branch November 19, 2024 08:51
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.

1 participant