You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prior to #1639, you could refer to MSALInternalErrorAuthorizationFailed from Swift via MSALInternalError.errorAuthorizationFailed. The PR added some new cases that started with the prefix MSALError instead of MSALInternalError and that seems to have changed how the pre-existing cases are imported into Swift such that you now have to write: MSALInternalError.internalErrorAuthorizationFailed.
There's also MSALInternalBrokerNotAvailable which lacks the full prefix. I suspect that if all the cases used the full MSALInternalError prefix, then in Swift you could write MSALInternalError.authorizationFailed.
It's not hard for developers to update their code accordingly when updating, but these issues do lead to source-breaking changes.
To detect these issues earlier, it would be good to set up automated breaking change detection for the generated Swift API.
The text was updated successfully, but these errors were encountered:
Prior to #1639, you could refer to
MSALInternalErrorAuthorizationFailed
from Swift viaMSALInternalError.errorAuthorizationFailed
. The PR added some new cases that started with the prefixMSALError
instead ofMSALInternalError
and that seems to have changed how the pre-existing cases are imported into Swift such that you now have to write:MSALInternalError.internalErrorAuthorizationFailed
.There's also
MSALInternalBrokerNotAvailable
which lacks the full prefix. I suspect that if all the cases used the fullMSALInternalError
prefix, then in Swift you could writeMSALInternalError.authorizationFailed
.It's not hard for developers to update their code accordingly when updating, but these issues do lead to source-breaking changes.
To detect these issues earlier, it would be good to set up automated breaking change detection for the generated Swift API.
The text was updated successfully, but these errors were encountered: