We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It should be a top-level option:
newsletter: { component: true, // mailchimp | revue | buttondown <YOUR_NEWSLETTER_PROVIDER>: { // options like apiKey } }
Also, you could support the provider prop in the component to use one of the providers defined (default to the first one defined).
provider
The text was updated successfully, but these errors were encountered:
Hey @Atinux
Thanks for the recomendation.
The component option as the top level seems like a very good idea!
In terms of provider in components, I dont think it is possible as the provider is used to define the server middleware that should be used.
Sorry, something went wrong.
No branches or pull requests
It should be a top-level option:
Also, you could support the
provider
prop in the component to use one of the providers defined (default to the first one defined).The text was updated successfully, but these errors were encountered: