Merge with upstream#5
Draft
AdriVanHoudt wants to merge 500 commits into
Draft
Conversation
The Event API, in addition to support for manually-added conference details, supports auto generating conference details. If you have an integration authorized and enabled for your Nylas account you can provide an autocreate object instead of a details object to have the Nylas API autofill the conferencing details.
New nylas v5.7.0 release: * Fix minor issues with Neural API implementation * Fix not rejecting uncaught errors during requests * Add missing fields for recurring events * Add support for conferencing
The conditional logic in the RestfulModel toJSON method was not explicit enough on the value of enforceReadOnly, leading to JSON.stringify unintentionally ignoring read only values.
Updated readme links and removed pages that don't exist anymore
…272) JSON.parse(req.rawBody) was throwing an error if req.rawBody was an empty string.
This PR addresses an issue that causes some PUT calls for Calendar objects to break. The issue was found when a customer was unable to update an event on API 2.2 with the API rejecting the call because message_id was present in the body. The messageId property is supposed to be readonly. We have 5 properties in Calendar that are now marked as readonly: messageId, owner, iCalUID, status, and jobStatusId
This PR enables support for the /calendars/availability/consecutive endpoint.
New nylas v5.8.0 release
This PR enables SDK support for the Scheduler API.
This PR enables SDK support for the Nylas /component endpoints.
* Update CHANGELOG.md * 5.9.0
Add support for Event notifications.
The metadata feature first introduced for events has expended to Calendar and Account. This PR adds support for this change. More information on the expansion of the metadata can be found here: https://developer.nylas.com/docs/developer-tools/api/metadata
This PR adds the remaining Scheduler endpoints
The Nylas API now supports metadata for existing messages. This is a followup to #286.
New nylas v5.10.0 release
The Scheduler booking timeslot endpoint requires the booking request payload to include a value for additional_emails and additional_values even if they are set to empty or null. This PR sets them to a blank array/object to avoid this error.
New nylas v5.10.1 patch release
A recent API update caused updating an event using the SDK to return an error because the SDK sends a Participant's status as well as an object key within the Event.when object.
A couple of Scheduler and Component types were incorrect or missing. This PR also ensures modifiable fields are not sent when trying to update a component.
New nylas v5.10.2 patch release
This PR improves the Job Status support on this SDK. Some models are missing a job_status_id key, as well as the Job Status model itself was missing an original_data key. A new helper method was also introduced to the JobStatus object called isSuccessful() that returns a boolean value representing a successful job status.
The oauth/authorize endpoint supports a provider option for forcing authentication against a different provider, this PR adds it in.
New nylas v5.10.3 patch release
…tifications were not set (#298) Some recurring events throw an error from the API when sending an empty list of notifications. This could occur without the user setting an empty list of notifications as the Node SDK defaults all array-type attributes to an empty array even if not directly set the attribute. This PR overrides this functionality and prevents notifications from being set if the user did not explicitly set the attribute.
New nylas v5.10.4 patch release provides the following fix: * Prevent Event objects from sending an empty list of notifications when not set, causing errors for recurring events
This PR represents the major update v6.0.0 of the Node SDK. The main theme of this major release is refactoring and improving the SDK to make it more Typescript-like as well as improving the usability of the SDK by providing better and stricter type hinting as well as expected parameters. This major release can be broken down into three main sections: refactoring RestfulModel, improving deserialization and object creation, and improving the typing of the SDK in general.
…305) This PR enables two new fields in EventParticipant, comment and phoneNumber. More detail can be found in the API reference.
saveRequestBody() was introduced prior to the v6.0 release to enforce read-only attributes not being serialized for outgoing API calls. With the introduction of the Model superclass in v6.0 a lot of objects got refactored from extending RestfulModel to Model, but saveRequestBody() remained on RestfulModel. This broke the serialization of Model properties. To resolve this, we moved saveRequestBody() to the Model superclass.
…arams. (#686) Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…alendars (#688) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Aaron de Mello <314152+AaronDDM@users.noreply.github.com>
…e-vite-calendars (#687) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Aaron de Mello <314152+AaronDDM@users.noreply.github.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Yunus Szönyi <yunus@hellomateo.de>
Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…ink to developer.nylas.com (#728) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For Salesflare/Server#4012