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

Make from field Optional to not cause Key errors #382

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

kraju3
Copy link
Contributor

@kraju3 kraju3 commented Sep 5, 2024

Description

https://nylas.zendesk.com/agent/tickets/94722

License

I confirm that this contribution is made under the terms of the MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@AaronDDM
Copy link
Contributor

AaronDDM commented Sep 5, 2024

@kraju3 is this expected API behaviour...? seems odd, doesn't it? Or does it happen for drafts?

@kraju3
Copy link
Contributor Author

kraju3 commented Sep 5, 2024

@AaronDDM It seems like Microsoft Graph API sometimes omit this value from their response and we won't translate it on our end. Since the field is not typed to optional our SDK throws a KeyError while decoding and users won't be able to process the response via the SDK. Making it Optional will solve the KeyError so that they can at least enrich the data.

@mrashed-dev mrashed-dev merged commit 6955356 into nylas:main Sep 9, 2024
3 of 4 checks passed
@mrashed-dev mrashed-dev mentioned this pull request Sep 24, 2024
mrashed-dev added a commit that referenced this pull request Sep 24, 2024
* Add support for from field for sending messages (#386)
* Add missing schedule-specific fields to Message model (#385)
* Add migration grant properties (#387)
* Fix from field not being optional causing deserialization errors (#382)
* Fix IMAP identifiers not encoding correctly (#383)
* Fix NylasOAuthError not setting the status code properly (#388, #379)
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.

3 participants