Skip to main content

This is a contributors guide and NOT a user guide. Please visit these docs if you are using or evaluating SuperTokens.

Recipe config management functions when the recipe is disabled in core


This is just a proposal so far, it hasn't been accepted and needs further discussion.

rishabhpoddar, sattvikc
Proposed by:

Context and Problem Statement#

In the context of thirdparty, should management of dynamic provider list be allowed when the thirdparty recipe is disabled in core?

Considered Options#

  • Should not be allowed
  • Should be allowed

Decision Outcome#

Chosen option: Should be allowed, because

  • it is a better developer experience (less restricting)

Pros and Cons of the Options#

Should not be allowed#

  • User will be forced to enable a recipe before adding its configs
  • Should be allowed#

  • Better user experience as she can add/update all the configs and then enable the recipe
  • Looking for older versions of the documentation?
    Which UI do you use?
    Custom UI
    Pre built UI