Skip to content

Conversation

@bjohansebas
Copy link
Member

Summary

I’m removing this TODO that was there. I still need to investigate whether the next TODO actually exists and fix it if so. Now that it returns other things, I think we should change the name, what do you think?

What kind of change does this PR introduce?

Did you add tests for your changes?

Does this PR introduce a breaking change?

If relevant, what needs to be documented once your changes are merged or what have you already documented?

@codecov
Copy link

codecov bot commented Jan 25, 2026

Codecov Report

❌ Patch coverage is 76.92308% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 95.83%. Comparing base (76b77c6) to head (a244fb0).
⚠️ Report is 1 commits behind head on next.

Files with missing lines Patch % Lines
src/utils/getFilenameFromUrl.js 62.50% 3 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##             next    #2253   +/-   ##
=======================================
  Coverage   95.83%   95.83%           
=======================================
  Files          13       13           
  Lines         888      888           
  Branches      259      258    -1     
=======================================
  Hits          851      851           
  Misses         37       37           

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

@bjohansebas
Copy link
Member Author

Moving back to draft because we need to use new URL() and stop using url.parse()

@bjohansebas bjohansebas marked this pull request as draft January 26, 2026 22:49
@bjohansebas bjohansebas force-pushed the bsebas/todoAboutFilename branch from ae62110 to a244fb0 Compare January 27, 2026 02:11
@bjohansebas bjohansebas force-pushed the bsebas/todoAboutFilename branch from 85bcecc to f56758e Compare January 27, 2026 04:29
@bjohansebas
Copy link
Member Author

Okay, for now one test is failing. When publicPath is defined, the behavior of using new URL is more different than I expected. We need to make sure it doesn’t imply additional changes, because new URL is not a direct replacement for url.parse.

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