From c6ab0c6ec5208dc09140245ecbd7d2b96d4a4d0d Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 9 Apr 2026 19:26:18 +0000 Subject: [PATCH] Fix operator precedence bug in isMobileStaticRecalibrationApplicable on schedule page The schedule.vue computed property had incorrect parenthesization that caused isCashItacNoComp and mobileFeePart?.isInsurable to be evaluated as top-level OR alternatives instead of being gated behind the displayMSR experiment flag and MOBILE_STATIC_RECAL_FEE part number check. Before (buggy): (displayMSR && partNumber == RECAL_FEE && enableMSRSplitPay) || isCashItacNoComp || mobileFeePart?.isInsurable After (fixed): displayMSR && partNumber == RECAL_FEE && (enableMSRSplitPay || isCashItacNoComp || mobileFeePart?.isInsurable) This aligns schedule.vue with the correct logic in service-location.vue and service-location-june-2025.vue, preventing unnecessary mobile schedule API calls for orders where recalibration cannot be done mobile. Co-authored-by: Mark Harris --- src/layouts/schedule/schedule.vue | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/src/layouts/schedule/schedule.vue b/src/layouts/schedule/schedule.vue index f5462fb9e..c483c90df 100644 --- a/src/layouts/schedule/schedule.vue +++ b/src/layouts/schedule/schedule.vue @@ -705,11 +705,9 @@ export default { }, isMobileStaticRecalibrationApplicable() { return ( - (this.displayMSR && - this.mobileFeePart?.partNumber == partNumberStrings.MOBILE_STATIC_RECAL_FEE && - this.enableMSRSplitPay) || - this.isCashItacNoComp || - this.mobileFeePart?.isInsurable + this.displayMSR && + this.mobileFeePart?.partNumber == partNumberStrings.MOBILE_STATIC_RECAL_FEE && + (this.enableMSRSplitPay || this.isCashItacNoComp || this.mobileFeePart?.isInsurable) ); }, displayMSR() {