Skip to content
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

Add messaging providers route #602

Merged
merged 9 commits into from
Jan 2, 2024

Conversation

stnguyen90
Copy link
Contributor

@stnguyen90 stnguyen90 commented Oct 24, 2023

What does this PR do?

Add messaging providers route

Test Plan

TBD

Related PRs and Issues

Parent:

Children:

Have you read the Contributing Guidelines on issues?

Yes

@stnguyen90 stnguyen90 marked this pull request as draft October 24, 2023 23:57
@vercel
Copy link

vercel bot commented Oct 24, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
console ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 2, 2024 2:53pm
console-cloud 🛑 Canceled (Inspect) Jan 2, 2024 2:53pm
console-preview ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 2, 2024 2:53pm
console-preview-cloud 🛑 Canceled (Inspect) Jan 2, 2024 2:53pm

{ id: 'status', title: 'Status', show: true }
]);

export const providers = {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TorstenDittmann, what do you think about having this JSON for the wizard for all providers. I wanted to try and minimize the number of places you'd need to go if we add a messaging provider in the future.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Torsten: for now, let's continue with this.

try {
let response = { $id: '', name: '' };
const providerId = $providerParams[$provider].providerId || ID.unique();
switch ($provider) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TorstenDittmann, this is going to be long and annoying because there's a different method for each provider. Any thoughts on how to improve this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Torsten: for now, let's go with this.

Comment on lines 28 to 103
export const providerParams = writable<{ mailgun: Partial<MailgunProviderParams> }>({
mailgun: null
});
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TorstenDittmann, I wanted to do this to make the create/update part easier, but do you think it's not worth it and I should just have a writable for each provider?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Torsten: for now, let's go with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants