Closed oliverdrummond closed 1 month ago
This type was never part of the public surface so you should not be dependent on it. Some of the implementation details of the interceptor needed to change to fix some bugs which is why this was removed.
Can you help me understand the impact of its removal to your specific requirements so I might suggest an alternative approach using API stable exports?
@oliverdrummond This issue has been automatically marked as stale because it is marked as requiring author feedback but has not had any activity for 5 days. If your issue has been resolved please let us know by closing the issue. If your issue has not been resolved please leave a comment to keep this open. It will be closed automatically in 7 days if it remains stale.
Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
msal-angular-v3.0.23
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
msal-angular-v3.0.23
Public or Confidential Client?
Public
Description
Until v3.0.18,
msal.interceptor.config.ts
had the export forMatchingResources
On version 3.0.19 the export was removed and still not available on v3.0.23
Error Message
TS2305: Module '"@azure/msal-angular/msal.interceptor.config"' has no exported member 'MatchingResources'.
MSAL Logs
No response
Network Trace (Preferrably Fiddler)
MSAL Configuration
Relevant Code Snippets
Reproduction Steps
Expected Behavior
Keep the exported type or provide an alternative
Identity Provider
Entra ID (formerly Azure AD) / MSA
Browsers Affected (Select all that apply)
Chrome, Firefox, Edge, Safari
Regression
3.0.18
Source
External (Customer)