Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(assert): move unstable assertNever under @std/assert/unstable-never #5928

Merged
merged 2 commits into from
Sep 11, 2024

Conversation

kt3k
Copy link
Member

@kt3k kt3k commented Sep 10, 2024

part of #5920

This PR moves assertNever under the export path assert/unstable-never

Copy link

codecov bot commented Sep 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.25%. Comparing base (b3e1ebb) to head (7d35dff).
Report is 7 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5928      +/-   ##
==========================================
- Coverage   96.25%   96.25%   -0.01%     
==========================================
  Files         489      489              
  Lines       39457    39456       -1     
  Branches     5824     5823       -1     
==========================================
- Hits        37980    37978       -2     
- Misses       1433     1434       +1     
  Partials       44       44              

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

@iuioiua iuioiua changed the title refactor(assert): move unstable assertNever under 'unstable-never' refactor(assert): move unstable assertNever under @std/assert/unstable-never Sep 10, 2024
@kt3k kt3k merged commit 780deaf into denoland:main Sep 11, 2024
17 checks passed
@kt3k kt3k deleted the refactor-move-assert-never-under-unstable branch September 11, 2024 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants