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] More verbs/nouns fixes in disambiguation.xml #11073

Merged
merged 1 commit into from
Nov 30, 2024

Conversation

marcoagpinto
Copy link
Member

@marcoagpinto marcoagpinto commented Nov 30, 2024

More fixes.

Summary by CodeRabbit

  • New Features

    • Introduced new rule groups for enhanced disambiguation of specific Portuguese verbs.
    • Updated rules to improve the accuracy of identifying nouns as verbs.
  • Bug Fixes

    • Refined existing rules to remove incorrect tags from verbs in various contexts.

These changes significantly improve the language processing capabilities for Portuguese, ensuring more accurate grammar checks.

Copy link
Contributor

coderabbitai bot commented Nov 30, 2024

Walkthrough

The pull request introduces extensive modifications to the disambiguation.xml file for Portuguese language rules in LanguageTool. It includes the addition of new rule groups aimed at refining verb disambiguation, updates to existing rules to enhance accuracy, and the removal of outdated rules. The changes focus on improving the handling of specific verbs and their contexts, with numerous examples provided to illustrate the intended functionality.

Changes

File Path Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml - Added rule groups: REMOVE_PODAR_FROM_MODAL_PODER, REMOVE_BASTIR_FROM_BASTAR, REMOVE_IRIAR_FROM_IR
- Updated rules: VERB_VNOUN_NOUN_VERBS_RARE, PELA_COMO_SOBRE_NADA_ACERCA_ELAR_VERBS_RARE, PELA_COMO_SOBRE_NADA_ACERCA_ELAR_PUREVERBS_VERBS_RARE
- Removed certain outdated rules.

Possibly related issues

Possibly related PRs

Suggested reviewers

  • jaumeortola
  • 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 (3)
languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml (3)

3933-3957: Consider adding more test examples for the disambiguation rules.

The rule groups for handling verb disambiguation look good, but would benefit from more comprehensive test examples to ensure proper coverage of edge cases.

Consider adding examples like:

<example type="ambiguous" inputform="pode[podar/VMM03S0,poder/VMIP3S0]" outputform="pode[poder/VMIP3S0]">Ele não <marker>pode</marker> fazer isso.</example>
<example type="untouched">Ele <marker>poda</marker> as plantas.</example>

Line range hint 3933-4024: Optimize pattern matching in verb disambiguation rules.

The rules for handling verb/noun disambiguation are well-structured but could be optimized for better performance.

Consider these optimizations:

  1. Combine similar pattern matches using the | operator
  2. Use more specific postag patterns where possible
  3. Consider adding <antipattern> blocks for common false positives

Example optimization:

-<token postag="VMSP3S0|VMIP3S0|VMM02S0|VMSP2S0|VMIP2S0|VMN02S0|VMSF2S0" postag_regexp="yes"/>
+<token postag="VM[SIM][PIF][23]S0|VMN02S0" postag_regexp="yes"/>

Line range hint 1-4024: Enhance rule documentation for better maintainability.

While the code is well-organized, some rules would benefit from more detailed documentation explaining:

  • The linguistic rationale behind the rule
  • Examples of what the rule catches and doesn't catch
  • Any known limitations or edge cases

Consider adding structured comments like this before complex rules:

<!-- Rule: REMOVE_PODAR_FROM_MODAL_PODER
     Purpose: Disambiguates between 'podar' (to prune) and 'poder' (can/may)
     Context: When 'poder' is used as a modal verb followed by an infinitive
     Example matches:
       - "pode fazer" -> poder (can do)
       - "pode estar" -> poder (may be)
     Non-matches:
       - "poda as plantas" -> podar (prunes the plants)
     Known limitations:
       - May need special handling for reflexive verbs
-->
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f02c55e and 336ee4f.

📒 Files selected for processing (1)
  • languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml (1 hunks)

@marcoagpinto marcoagpinto merged commit 1cabb34 into master Nov 30, 2024
5 checks passed
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