-
Notifications
You must be signed in to change notification settings - Fork 239
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
Neon frontend #4624
Neon frontend #4624
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
<Modal closeModal={onClose} width={"800px"}> | ||
<Text size={16}>Integrate Neon</Text> | ||
<Spacer y={0.5} /> | ||
<Text color="helper"> | ||
To continue, you must authenticate with Neon.{" "} | ||
<Link target="_blank" onClick={openAuthWindow} hasunderline> | ||
Authorize Porter to create Neon datastores on your behalf | ||
</Link> | ||
</Text> | ||
</Modal> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it worth showing this modal in a blocked / loading state after they go through the flow with neon, so they don't end up proceeding before we save the integration on our end?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
they cant proceed; if they click create again, they'll just see the same modal
user can auth with neon, create neon datastore, see credentials and delete it