Repository navigation
[#874] Removed the 'field_parser: legacy' parser. - #880
Conversation
|
Warning Review limit reached
More reviews will be available in 18 minutes and 40 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (10)
📝 WalkthroughWalkthroughRemoves the ChangesLegacy field parser removal
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
a5d7d8a to
e08a822
Compare
|
Documentation validation Per-context details |
|
Code coverage (threshold: 70%) Per-class coverage |
Closes #874
Summary
Removes the
field_parser: legacyextension parameter and its backingLegacyEntityFieldParserclass as part of the 6.1.0 deprecation removals. Thefield_parserconfig node introduced in 6.0.0 allowed opting back into the pre-v6 inline field syntax during migration; that migration window is now closed.EntityFieldParseris the only parser, it is always active, and no configuration is needed or accepted.Changes
LegacyEntityFieldParserand its full unit test (LegacyEntityFieldParserTest).field_parserenumNodefromDrupalExtension::configure(), so anyfield_parserkey inbehat.ymlnow causes a hard configuration error on load.RawDrupalContext::getFieldParser()to unconditionally return anEntityFieldParser; removed theLegacyEntityFieldParserimport and thefield_parserbranch.behatCliUseLegacyFieldParser()fromBehatCliTraitand thefield_parser: legacyentry frombehat.dist.yml.field_handlers_legacy.feature(five legacy-parser subprocess scenarios that no longer have a code path to exercise).UPGRADING.md: removed the 6.0 "Configuration" section that documented thefield_parserswitch, added a 6.1 "Field parser:legacyparser removed" section with a before/after YAML snippet and a pointer to the field-syntax table. UpdatedParser/README.mdto reflect a single parser with no configuration.Before / After
Summary by CodeRabbit
Release Notes
Breaking Changes
field_parseroption must be removed entirelyDocumentation