-
Notifications
You must be signed in to change notification settings - Fork 4k
Apply Azure AD, B2C changes on next to fix provider semantics #1591
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
Apply Azure AD, B2C changes on next to fix provider semantics #1591
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nextauthjs/next-auth/6ymYPZcyqTr698h19JC9WTEcZZVL |
|
Not sure why the Vercel deployment fails, I switched to your branch locally, and the build was successful. 🤷 Error log from Vercel12:33:49.710 | ✔ Client: Compiled with some errors in 31.73s 12:33:49.713 | ./src/theme/SearchBar/algolia.css 12:33:49.713 | URIError: URI malformed 12:33:49.714 | at decodeURI () 12:33:49.714 | @ ./src/theme/SearchBar/index.js 12:345-368 12:33:49.714 | @ ./node_modules/@docusaurus/theme-classic/lib-next/theme/Navbar/index.js 12:33:49.714 | @ ./node_modules/@docusaurus/theme-classic/lib-next/theme/Layout/index.js 12:33:49.714 | @ ./node_modules/@docusaurus/theme-classic/lib-next/theme/NotFound.js 12:33:49.714 | @ ./node_modules/@docusaurus/core/lib/client/exports/ComponentCreator.js 12:33:49.714 | @ ./.docusaurus/routes.js 12:33:49.714 | @ ./node_modules/@docusaurus/core/lib/client/clientEntry.js 12:33:49.714 | @ multi ./node_modules/@docusaurus/core/lib/client/clientEntry.js 12:33:49.715 | Client bundle compiled with errors therefore further build is impossible. 12:33:49.715 | ./src/theme/SearchBar/algolia.css 12:33:49.715 | Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js): 12:33:49.715 | ModuleBuildError: Module build failed (from ./node_modules/css-loader/dist/cjs.js): 12:33:49.715 | URIError: URI malformed 12:33:49.715 | at /vercel/workpath0/www/src/theme/SearchBar/algolia.css:522:3 12:33:49.715 | at decodeURI () 12:33:49.715 | at normalizeUrl (/vercel/workpath0/www/node_modules/css-loader/dist/utils.js:114:10) 12:33:49.715 | at /vercel/workpath0/www/node_modules/css-loader/dist/plugins/postcss-url-parser.js:119:37 12:33:49.716 | at walk (/vercel/workpath0/www/node_modules/postcss-value-parser/lib/walk.js:7:16) 12:33:49.716 | at ValueParser.walk (/vercel/workpath0/www/node_modules/postcss-value-parser/lib/index.js:18:3) 12:33:49.717 | at parseDeclaration (/vercel/workpath0/www/node_modules/css-loader/dist/plugins/postcss-url-parser.js:97:10) 12:33:49.717 | at Declaration (/vercel/workpath0/www/node_modules/css-loader/dist/plugins/postcss-url-parser.js:248:29) 12:33:49.717 | at LazyResult.visitTick (/vercel/workpath0/www/node_modules/postcss/lib/lazy-result.js:456:16) 12:33:49.717 | at LazyResult.runAsync (/vercel/workpath0/www/node_modules/postcss/lib/lazy-result.js:372:30) 12:33:49.717 | at LazyResult.async (/vercel/workpath0/www/node_modules/postcss/lib/lazy-result.js:205:30) 12:33:49.717 | at LazyResult.then (/vercel/workpath0/www/node_modules/postcss/lib/lazy-result.js:190:17) 12:33:49.717 | at /vercel/workpath0/www/node_modules/webpack/lib/NormalModule.js:316:20 12:33:49.717 | at /vercel/workpath0/www/node_modules/loader-runner/lib/LoaderRunner.js:367:11 12:33:49.717 | at /vercel/workpath0/www/node_modules/loader-runner/lib/LoaderRunner.js:233:18 12:33:49.717 | at context.callback (/vercel/workpath0/www/node_modules/loader-runner/lib/LoaderRunner.js:111:13) 12:33:49.717 | at Object.loader (/vercel/workpath0/www/node_modules/css-loader/dist/index.js:154:5) UPDATE: |
|
@balazsorban44 is this Types lint error a known issue? Unsure if I should do something in my code to fix that or if it will be fixed elsewhere on |
|
Yes, I guess it is "expected"... I am experimenting with cutting the |
|
NOTE to other maintainers: When merging, we should to point out the breaking changes here, following the https://www.conventionalcommits.org/en/v1.0.0/ |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## next #1591 +/- ##
=========================================
- Coverage 10.05% 9.95% -0.11%
=========================================
Files 81 82 +1
Lines 1382 1396 +14
Branches 387 390 +3
=========================================
Hits 139 139
- Misses 1022 1033 +11
- Partials 221 224 +3 ☔ View full report in Codecov by Sentry. |
balazsorban44
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, @BenjaminWFox! Sorry for being slow on this, but I would like to pick this up now and get this merged! I had a simple comment, could you address that? If everything is fine, then I'll merge this ASAP, to get things ready for next-auth@4... 👀
BREAKING CHANGE: If you currently use `AzureADB2C`, you will need to update it to to `AzureAD` There should be no other changes needed.
What:
Created new provider
azure-adcontaining what was previouslyazure-ad-b2cUpdated content for provider
azure-ad-b2cto reflect correct configuration for that providerWhy:
#1586
How:
Changes to Provider JS & MD files, and updating the provider index.
Checklist:
next* This will probably be a breaking change *
Anyone who previously has implemented what is currently provider
azure-ad-b2c/Providers.AzureADB2Cwill need to update their provider to beazure-ad/Providers.AzureAD. There should be no other changes needed.