fix: allow static assets through wsist.ch middleware - #37
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe marketing-site middleware in Marketing Site & SDK Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
allowedOnMarketingpath list in thewsist.chmiddleware block to include static asset prefixes (/_framework,/_content,/_blazor,/app.css,/landing.css,/landing.js,/logo.svg,/favicon,/WSIST.Web.styles.css)wsist.ch/caused by the middleware redirecting JS/CSS requests back to/instead of serving themglobal.jsonSDK version to match the locally installed10.0.109SDKTest plan
dotnet test— 35 tests passdotnet csharpier format .— no formatting changes neededwsist.ch/and confirm the landing page loads with no console errorswsist.ch/login-pagestill loads correctlyapp.wsist.chare unaffected🤖 Generated with Claude Code
Summary by CodeRabbit
Bug Fixes
Chores