[#291] Fixed 'EntityReferenceHandler' crash when entity label key is FALSE.#308
[#291] Fixed 'EntityReferenceHandler' crash when entity label key is FALSE.#308AlexSkrypnyk merged 1 commit intomasterfrom
Conversation
…hen label key is FALSE.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 47 minutes and 6 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Summary
EntityReferenceHandler::expand()when the referenced entity type has no label key (i.e.,getKey('label')returnsFALSE).commerce_licensedo not define a label key, which previously caused an invalidorConditionGroupwith anOR FALSEcondition appended, crashing the entity query.$label_keyisFALSE, the handler now falls back to a simple ID-only condition instead of building anorConditionGroup.Problem
Entity types that return
FALSEforgetKey('label')triggered this code path:Passing
FALSEas a field name to$or->condition()caused a fatal error or an invalid query.Fix
The query-building block is now guarded by a
$label_keycheck:When
$label_keyis falsy, the handler matches by ID only, which is the only sensible fallback for entities with no label field.Related