Fix field type name in readme

[Crabcyborg]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@Crabcyborg has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 6 minutes and 9 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 6e8bbe5 and d0d07e7.

📒 Files selected for processing (1)

• rector.php

Walkthrough

Updated documentation wording in v6.27 changelog/readme and adjusted Rector PHP configuration to import a new rule class and remove it from a skip list; no public API or runtime behavior changes.

Changes

Cohort / File(s)	Summary
Changelog / Readme changelog.txt, readme.txt	Text change: replaced "rank field" with "ranking field" in the v6.27 release notes entries.
Rector configuration rector.php	Configuration update: added AddReturnDocblockForDimFetchArrayFromAssignsRector to imports and removed it from the TypeDeclarationDocblocks skip list.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Remove some rector exceptions #2614: Similar edits to rector.php imports and skip lists for Rector rules.
• Add rector rule to explicitly return null #2668: Related changes adjusting Rector rule enablement and configuration.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No pull request description was provided by the author, which is a missed opportunity to explain the context and rationale for the changes.	Consider adding a brief description explaining why the field type name was changed from 'rank field' to 'ranking field' for better context.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Fix field type name in readme' accurately describes the main change: updating field type name wording in documentation files (changelog.txt and readme.txt).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

readme.txt (1)

374-387: Good doc fix; matches the “Ranking” field terminology.
No behavior impact, and this improves consistency/clarity for users reading the 6.27 notes.

Optional nit: consider “Ranking field” (capital R) if you want changelog wording to match the UI/field label casing used elsewhere in the doc.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1908954 and 7f5787c.

📒 Files selected for processing (2)

• changelog.txt
• readme.txt

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: PHP 8 tests in WP 6.9
• GitHub Check: PHP 7.4 tests in WP 6.9
• GitHub Check: Cypress
• GitHub Check: PHP 7.4 tests in WP 6.9
• GitHub Check: PHP 8 tests in WP 6.9
• GitHub Check: PHP 8 tests in WP 6.9
• GitHub Check: PHP 7.4 tests in WP 6.9
• GitHub Check: Cypress
• GitHub Check: Cypress

🔇 Additional comments (1)

changelog.txt (1)

1-13: LGTM—consistent terminology update (“ranking field”).
No functional impact; keeps the 6.27 notes accurate and aligned with the product naming.