-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Return ResolvedKeystoneConfig instead of KeystoneConfig #9189
base: main
Are you sure you want to change the base?
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit f5fbd04:
|
56e0979
to
a0740f4
Compare
a0740f4
to
068c5d3
Compare
ab63849
to
395c861
Compare
395c861
to
946347e
Compare
946347e
to
71a12f8
Compare
Do we actually need to break? The resolved type is only a type refinement, hopefully |
we can do minor change for this, as no one was using until now. |
71a12f8
to
f5fbd04
Compare
@dcousens I have updated this to be minor instead of major change. |
34263d9
to
908dc13
Compare
b43d0a2
to
139fce4
Compare
__ResolvedKeystoneConfig
toResolvedKeystoneConfig
;config
function so that any config wrapper can make use of defaults.config()
now returnsResolvedKeystoneConfig
instead ofKeystoneConfig
withAuth
input now needsResolvedKeystoneConfig
Breaking changes due to type change, There is no migration needed in most cases instead of type casting in some case.