Skip to content

Add variable coercion backwards compatibility#9289

Merged
michaelstaib merged 3 commits intomainfrom
mst/variable-coercion-legacy
Mar 2, 2026
Merged

Add variable coercion backwards compatibility#9289
michaelstaib merged 3 commits intomainfrom
mst/variable-coercion-legacy

Conversation

@michaelstaib
Copy link
Copy Markdown
Member

No description provided.

items.Add(CoerceInputLiteral(item, elementType, context, elementDepth));
}
}
else
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should gate this. We don't want new projects to introduce this issue again, it should be exclusively for existing projects that wouldn't be able to upgrade due to old client operations.

@michaelstaib michaelstaib merged commit bb123ab into main Mar 2, 2026
117 checks passed
@michaelstaib michaelstaib deleted the mst/variable-coercion-legacy branch March 2, 2026 20:28
@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (f2873e8) to head (cc4ed2b).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@     Coverage Diff      @@
##   main   #9289   +/-   ##
============================
============================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants