Skip to content

[CLIENT-4344] Add deprecation warning that ResultsRemove() expression will be renamed to RemoveResults() in the next major client release#997

Open
juliannguyen4 wants to merge 3 commits intodevfrom
CLIENT-4344-warn-that-resultremove-expression-will-be-renamed-to-removeresult
Open

[CLIENT-4344] Add deprecation warning that ResultsRemove() expression will be renamed to RemoveResults() in the next major client release#997
juliannguyen4 wants to merge 3 commits intodevfrom
CLIENT-4344-warn-that-resultremove-expression-will-be-renamed-to-removeresult

Conversation

@juliannguyen4
Copy link
Collaborator

No description provided.

@juliannguyen4 juliannguyen4 force-pushed the CLIENT-4344-warn-that-resultremove-expression-will-be-renamed-to-removeresult branch from d805929 to 7c963a3 Compare March 20, 2026 15:56
@codecov-commenter
Copy link

codecov-commenter commented Mar 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.83%. Comparing base (88dadfa) to head (9563453).
⚠️ Report is 6 commits behind head on dev.

Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #997      +/-   ##
==========================================
+ Coverage   83.48%   83.83%   +0.34%     
==========================================
  Files          99       99              
  Lines       14402    14429      +27     
==========================================
+ Hits        12024    12096      +72     
+ Misses       2378     2333      -45     

☔ 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.

@juliannguyen4 juliannguyen4 marked this pull request as ready for review March 20, 2026 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants