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] Small fix in disambiguation.xml #11196

Merged
merged 1 commit into from
Jan 17, 2025

Conversation

marcoagpinto
Copy link
Member

@marcoagpinto marcoagpinto commented Jan 17, 2025

Small fix in the disambiguator.

Summary by CodeRabbit

  • Improvements
    • Enhanced Portuguese language disambiguation rules in LanguageTool
    • Refined verb and preposition identification accuracy
    • Added new context-specific rules for more precise language parsing

Copy link
Contributor

coderabbitai bot commented Jan 17, 2025

Walkthrough

The pull request modifies the Portuguese language disambiguation rules in the LanguageTool project. The changes focus on improving verb and token disambiguation within the disambiguation.xml file. The modifications include adding new rules, updating existing rules for tokens like "contra" and "a", and refining disambiguation actions to more accurately classify verbs and prepositions in different linguistic contexts.

Changes

File Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml - Added new rule VERB_NOUNVERB_SPS00_VERBS_RARE to remove rare verbs from appearing as main verbs
- Modified rule A_SPS to improve preposition identification
- Updated rule CONTRA to refine token disambiguation

Possibly related PRs

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
🪧 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: 1

🧹 Nitpick comments (1)
languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml (1)

3878-3883: Fix indentation of the disambig action.

The indentation of the <disambig> element is incorrect and should align with the <pattern> element.

-      <disambig action="add"><wd pos='VMIP3S0'/></disambig>
+    <disambig action="add"><wd pos='VMIP3S0'/></disambig>
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bfdaefa and f2933aa.

📒 Files selected for processing (1)
  • languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (java-kotlin)

Comment on lines +3884 to +3892
<rule> <!-- #3 -->
<pattern>
<token>outra</token>
<marker>
<token regexp='no'>vale</token> <!-- Add verbs as found -->
</marker>
<token postag='SPS.+|RG' postag_regexp='yes'/>
</pattern>
<disambig action="add"><wd pos='VMM02S0'/></disambig>
Copy link
Contributor

@coderabbitai coderabbitai bot Jan 17, 2025

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Remove duplicate rule.

This rule appears to be a duplicate of the previous one, with identical pattern and only a different verb form tag. Consider merging them into a single rule by adding both verb form tags.

-    <rule> <!-- #3 -->
-      <pattern>
-        <token>outra</token>
-        <marker>
-          <token regexp='no'>vale</token> <!-- Add verbs as found -->
-        </marker>
-        <token postag='SPS.+|RG' postag_regexp='yes'/>
-      </pattern>
-      <disambig action="add"><wd pos='VMM02S0'/></disambig>

Then modify the previous rule to include both verb forms:

     <rule> <!-- #2 -->
       <pattern>
         <token>outra</token>
         <marker>
           <token regexp='no'>vale</token> <!-- Add verbs as found -->
         </marker>
         <token postag='SPS.+|RG' postag_regexp='yes'/>
       </pattern>
-      <disambig action="add"><wd pos='VMIP3S0'/></disambig>
+      <disambig action="add">
+        <wd pos='VMIP3S0'/>
+        <wd pos='VMM02S0'/>
+      </disambig>

Committable suggestion skipped: line range outside the PR's diff.

Copy link
Member Author

Choose a reason for hiding this comment

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

The bot's suggestion didn't work.

Copy link
Contributor

Choose a reason for hiding this comment

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

@marcoagpinto I apologize for my incorrect suggestion. You were right to keep these as separate rules. Having distinct rules for each verb form (VMIP3S0 and VMM02S0) is actually clearer and more maintainable. The split approach also ensures proper disambiguation handling for each specific verb form. Please keep the rules separate as you originally implemented them.

¯\( ◕ ᴗ ◕ )


✏️ Learnings added
Learnt from: marcoagpinto
PR: languagetool-org/languagetool#11196
File: languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml:3884-3892
Timestamp: 2025-01-17T08:46:06.295Z
Learning: In Portuguese disambiguation rules, when handling multiple verb forms for the same pattern, use separate rules for each verb form tag instead of combining them with multiple <wd> tags in a single rule.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

@marcoagpinto marcoagpinto merged commit 75f1cfd into master Jan 17, 2025
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