Warning when obsolete msal-extensions is detected #752
+17
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The lengthy discussion in "Updates to msal/application.py may now be out-of-sync with msal_extensions"
#745 considered a mitigation of introducing a new optional dependency
msal[extensions]
for MSAL. However, after offline discussion, we believe it has two drawbacks: (1) it is hardly discoverable for mostmsal-extensions
users, and (2) it introduces a permanent "msal[extensions]" declaration only for trivial gain.So, we ended up settling on an alternative. MSAL will now detect the
msal-extensions
from the current environment. If its version is lower than 1.2.0, MSAL will emit a warning like this:This PR will close #745 .
CC @jiasli , @kcphila