-
Notifications
You must be signed in to change notification settings - Fork 232
Version 2.0.0 #179
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
Version 2.0.0 #179
Conversation
* Modified params passed in for initializaiton of MSAL provider - Breaking change * Fixed @nextlink property in Batching * Added negative value check for default values in retry and redirect handlers * Fixed - Auth handler replaces the authorization header * Fixed - Telemetry handler replaces the sdkVersion header
…ons to ImplicitMSALAuthenticationProvider and ImplicitMSALAuthenticationProviderOptions
…ionProviderOptions
|
Any ETA on the changes in this review? We're in an awkward place with this lib until this merges because of the old MSAL reference. |
|
Absolutely agree, spent some hours debugging mismatches today. Is there a dev release on npm to help test? |
|
@bitflower we haven't released in npm yet. will let you know once preview is released. |
|
Having the exact same issue as @bitflower as noted in this: #193 and am really needing this fix to be published. Do we have an ETA? |
|
@bitflower @mlynam @NoPhaseNoKill we have planned a preview release for v2.0.0 today. will update you once its released. |
|
Thanks for the help guys. Appreciate the release when it does go out :) |
|
That's great to hear, thanks! |
|
@bitflower @mlynam @NoPhaseNoKill Refer this release notes for the list of changes. |
|
Worked for my simple use case! Having a little trouble with my typescript imports though. Only got it to work like this: Repo: https://github.com/bitflower/stencil-ms-graph |
|
@bitflower I used the following import This is the method they suggest in the docs as well. |
|
@muthurathinam this is working for me now. I've only attempted to access the |
|
Thanks @mlynam your imports worked! |
|
This has resolved the scopes issue for me. Thanks guys, will let you know if any other issues! |
Yes @bitflower this is the feasible way as of now. |
New Features (Breaking Changes)
We are excited to announce that we will be releasing the preview for version 2.0.0 which will have the following changes
Polyfilling
Removed polyfills for Fetch and Promise, Now its the responsibility of the library users to polyfill these based on their environment support needs.
New minified files
graph-js-sdk-web.jsandgraph-js-sdk-core.jsfiles are no longer available, new file namedgraph-js-sdk.jswill be shipped along withgraph-es-sdk.js. Bothgraph-js-sdk.jsandgraph-es-sdk.jswill not depend on theisomorphic-fetchandes6-promiseanymore.Getting Raw Response
When making request using callback method raw response will not be passed as the param to the callback, instead one can get the same by using
.responseType(ResponseType.RAW).Renaming MSALAuthenticationProvider
Authentication provider and its options for MSAL library are now renamed from MSALAuthenticationProvider to ImplicitMSALAuthenticationProvider.
Initializing ImplicitMSALAuthenticationProvider
In order to create an instance of ImplicitMSALAuthenticationProvider previously named as MSALAuthenticaitonProvider. Now you can only pass an instance of MSAL's UserAgentApplication and MSALAuthenticationProviderOptions
Creating MSAL's UserAgentApplication
MSAL changed its way of initializing UserAgentApplication (also called as MSALInstance) in v1.0.0. Since we updated our MSAL's dependency to latest stable version and ImplicitMSALAuthenticationProvider modified to adapt the same. Creating instance of ImplicitMSALAuthenticationProvider takes UserAgentApplication created as per MSAL v1.0.0
Test plan
Closing issues
Types of changes
Checklist