Repository navigation
test(core): capture how docusaurus serve handles files with a dot and encoded slashes (AI-assisted) - #12898
Conversation
… encoded slashes (AI-assisted) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Caution Review failedThe pull request is closed. Walkthrough
Merge Risk:
|
✅ [V2]
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Size Change: 0 B Total Size: 12.1 MB ℹ️ View Unchanged
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
|
Size Change: 0 B Total Size: 12.1 MB ℹ️ View Unchanged
|
⚡️ Lighthouse report for the deploy preview of this PR
|
Motivation
The
docusaurus servetests capture folders with a dot in their name, but not files: this PR addsdocs/1.x.htmlto the fixture build, and captures the remaining edge cases before the stacked PRs fix them:trailingSlash: trueredirect, with or without abaseUrl:/base/docs/2.xservesdocs/2.x/index.htmldirectly, where/base/bothredirects to/base/both/. OurlooksLikeAssetregex and serve-handler both treat the dot as an extension.baseUrl: serve-handler decodes/base/%2F%2Ffileto//file, merges the slashes and redirects to/file, then the homepage.Files with a dot in their name are otherwise served like other files.
Test Plan
pnpm test packages/docusaurus/src/commands/serve: new snapshot rows and 3 edge case tests with aTODO fix.Test links
Deploy preview: https://deploy-preview-12898--docusaurus-2.netlify.app/
Related issues/PRs
docusaurus serveserves folders with a dot in their name (AI-assisted) #12896, which serves folders with a dot in their name(AI-assisted)
🤖 Generated with Claude Code
Summary by CodeRabbit