Repository navigation
chore: mark the query's path alias for removal in the next major release - #2485
Conversation
…lease Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UjuMAuk9o6UazjHzcAQCTA
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughA TODO comment documents the planned removal of query-string Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2485 +/- ##
=======================================
Coverage 96.59% 96.59%
=======================================
Files 24 24
Lines 2640 2640
=======================================
Hits 2550 2550
Misses 90 90 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Comment only. The client still reads
pathfrom its entry query as an alias ofurl, the name the query used in 8.3.0. This adds theTODO in the next major releasemarker next to that alias, so it is removed along with the other deprecated query names.setOptionsAndConnect({ path })is the runtime's own API and is not affected.No changeset: nothing user-facing changes.
Generated by Claude Code
Summary by CodeRabbit
pathoption is planned for removal in the next major release;setOptionsAndConnect({ path })remains the runtime API.