Npm @nylas/web-elements@2.2.1 bug

Question and Answers
1

I found the problem in the @nylas/web-elements package, version 2.2.1 - in the NylasScheduling component during the reschedule flow.

When booking an event, we get a booking_ref that we can use to reschedule the event. Using the NylasScheduling component in version 2.2.1 - the logic for decoding booking_ref to booking_id, configuration_id is broken under the hood - the values are unrealistic and corrupted, which results in the component crashing with an error that “configuration doesn’t exist”.

Steps to reproduce:

  1. Book an event based on a public configuration
  2. Take the bookingRef and insert it into the nylas-scheduling component - the @nylas/web-elements version must be 2.2.1, because in 2.1.0 everything works as expected.
  3. In the request - https://api.us.nylas.com/v3/scheduling/ui-settings you’ll see an error saying “configuration not found”.
  4. Compare your configuration ID with the configuration_id that was sent in the request above.

Please show this to your developers. The problem exists.

And yes, just to clarify - I tested with the same exact logic between versions 2.2.1 and 2.1.0

image
image834×808 31.1 KB

image

2

Hi @Oleksandr , you’re right - that is a bug, and we’re working on fixing it now. I’ll update you as soon as a fix has been released. Thank you for bringing it up!

1 Like
3

@nick.barraclough

Could you please pay attention to another one of my topics, there’s also a problem there. Link below:

4

Any update on this? It seems like there have been minor updates to the web-elements package (2.2.4 was released 8 days ago), but I’m still having this issue.

Also is there a github repository for the https://www.npmjs.com/package/@nylas/web-elements package?

5

Hi,

Are you getting the same booking not found error with the latest version?

Are you using our react components or the web elements directly, and do you have a minimal reproducible code by any chance?

Thank you