[pt] Added exceptions to rule ID:QUE_É-SÃO_NC-ADJ_COMO-POR

[marcoagpinto]

Added exceptions.

Summary by CodeRabbit

• New Features
  • Enhanced language style rules to include exceptions for specific Portuguese terms, improving accuracy in language processing.
  • Introduced a new antipattern for linking verb predicate agreement, addressing potential grammatical issues with specific tokens.

[coderabbitai]

Walkthrough

The pull request introduces changes to the XML configuration for the Portuguese language module by adding an <exception> element within a <token> element in the style.xml file. This modification specifies a regular expression for certain Portuguese words to enhance the specificity of language processing rules. Additionally, a new <antipattern> element is added to the grammar.xml file, which outlines linking verbs and associated grammatical issues.

Changes

File	Change Summary
languagetool-language-modules/pt/.../style.xml	Updated the <token> element to include an <exception regexp='yes'> sub-element with the regex: `fen[ôó]meno
languagetool-language-modules/pt/.../grammar.xml	Added a new <antipattern> element in the LINKING_VERB_PREDICATE_AGREEMENT rule group, including two <token> elements for linking verbs and related terms.

Possibly related PRs

• [pt] Added AP to rule ID:VERB_QUE_É_VERB_SER #11207: Involves modifications to the <style.xml> file, specifically the addition of new elements that enhance language rules.
• [pt] Added exceptions to rule ID:OS_DOIS_AS_DUAS_AMBOS_AMBAS #11149: Involves modifications to exception patterns within the style.xml file, indicating a direct relationship in handling token exceptions for Portuguese language rules.
• [pt] Added AP and exception to rule ID:PHD_TESE_PROCURAR_PROVAR_PROVARA #11188: Involves modifications to the <token> elements in the style.xml file, specifically adding exceptions to existing rules.

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

• 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/grammar.xml (1)

7857-7857: Formatting and Readability Check on New Line

The insertion at line 7857 appears to be an intentional extra line that improves readability. Please verify that this formatting is consistent with the overall file style.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8bf3f8b and e030f1d.

📒 Files selected for processing (1)

• languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/grammar.xml (1 hunks)

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

• GitHub Check: Analyze (java-kotlin)

🔇 Additional comments (2)

languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/grammar.xml (2)

7860-7865: New Antipattern Block: Validate Regex Patterns & Example

A new <antipattern> block has been introduced to capture linking verbs and related terms. Please ensure that:

• The token <token>que</token> is specific enough and does not lead to false positives considering that "que" is highly frequent in Portuguese.
• The regular expressions for linking verbs (e.g., andar|continuar|estar|ficar|parecer|permanecer|ser|tornar-se|virar|viver) and for additional terms (e.g., fen[ôó]meno|sensação|moda|hit|referência|mania|sucesso) are accurate and do not match unintended patterns.
• The example provided clearly demonstrates the intended rule behavior and its edge cases.

---

7866-7869: Additional Antipattern Block: Ensure Proper XML Closure and Schema Conformance

This block uses <antipattern> with tokens defined via postag attributes. Please verify that:

• The antipattern element is correctly closed later in the file (as the diff snippet does not show the closing tag).
• The XML structure remains well-formed and adheres to the project's schema.