This PR is primarily for discussion purposes, with code as a demonstration.
In the current implementation, if someone configures this provider using the global configuration shown in the README, they cannot then provide a different configuration at the call site. This is because the library overrides local / passed-in configuration options with the global config.
In my opinion, the library should prefer local over global [over the defaults]. This way, different call sites can provide their own options while still falling back to the global config. We intend to use this at CodeSandbox to provide logins via multiple Google OAuth clients โ one which is a clear default, and others which are specialized and locally configured.
Hello ๐๐ผ
This PR is primarily for discussion purposes, with code as a demonstration.
In the current implementation, if someone configures this provider using the global configuration shown in the README, they cannot then provide a different configuration at the call site. This is because the library overrides local / passed-in configuration options with the global config.
In my opinion, the library should prefer local over global [over the defaults]. This way, different call sites can provide their own options while still falling back to the global config. We intend to use this at CodeSandbox to provide logins via multiple Google OAuth clients โ one which is a clear default, and others which are specialized and locally configured.
Always open to feedback and discussion. Thanks!