-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[PM-8039] Fastmail: Change website default value to empty string. #9127
[PM-8039] Fastmail: Change website default value to empty string. #9127
Conversation
Thank you for your contribution! We've added this to our internal Community PR board for review. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Oh I see, I believe this issue would be fixed with the change here, since the default is now a string, but typescript is not my main thing, so let me know if I'm reading this wrong! |
I'd like this in the procedural code because the type definitions are in flux and this is fastmail-specific behavior. There's two spots for that at present. |
Fastmail API returns and error when passed a null value in forDomain. Empty string is the preferred blank option.
386a171
to
73c0a00
Compare
I updated this PR with the change in that other spot, but let me know if it makes more sense to close this one and open a PR against the other branch that's in progress. |
Sorry for the delay! For some reason your last push didn't come through my notifier! 😬 This is good to go! Thank you! :D |
@dixls - Looks like you need to sign the CLA with your fastmail account due to 73c0a00. I know they're both you, but we need our bot to know, too. 🙃 |
This reverts commit c37006c.
I think I got it now lol, whoops! Thanks so much! |
Thanks! |
Fastmail API returns and error when passed a null value in forDomain. Empty string is the preferred blank option.
Type of change
Objective
null
is not allowed in forDomain in Fastmail's API