This is a contributors guide and NOT a user guide. Please visit these docs if you are using or evaluating SuperTokens.
This is just a proposal so far, it hasn't been accepted and needs further discussion.
Should the additionalConfig (provider specific) (such as
hd for google workspaces,
teamId etc for apple) validated in core, while adding or updating them?
- Yes, Validate in core
- No provider specific validation in core
Chosen option: Yes, Validate in core, because
- Reduces run time error by ensuring that the correct config is added to the database
- No major drawback of this approach
This means that the core will validate the provider specific additionalConfig, before saving in the database. Also, adding a
noVerify flag to the core API to let the user skip the validation.