Skip to content
This repository has been archived by the owner on Apr 30, 2024. It is now read-only.

Releases: nabla/nabla-react-native

1.1.3

22 May 14:01
Compare
Choose a tag to compare

Added

Changed

Fixed

  • Fix a race condition that could lead to the following warning being sent by React Native: "Sending needProvideTokens with no listeners registered".
  • Fix a serialization issue for errors on iOS that would prevent displaying error details.

Versions

1.1.2

11 May 09:17
Compare
Choose a tag to compare

Added

Changed

Fixed

  • Android: Fix a bug leading to new messages and items not being fetched in real time when using clearCurrentUser.
  • iOS: Reverted Apollo library to version 0.51.2. Fixes cache issue preventing the loading of older conversation messages.

Versions

1.1.0

19 Apr 15:10
Compare
Choose a tag to compare

Added

  • Messaging core: Added new lastMessage property on Conversation that gives access to the whole message and not just its preview.
  • Add Portuguese translations

Changed

Fixed

  • The default Logger will now correctly print the error message if any.

Versions

1.0.1

21 Mar 15:45
Compare
Choose a tag to compare

[1.0.1] - 2023-03-21

Versions

1.0.0

17 Mar 13:53
Compare
Choose a tag to compare

[1.0.0] - 2023-03-17

Versions

1.0.0-alpha15

07 Mar 16:37
Compare
Choose a tag to compare
1.0.0-alpha15 Pre-release
Pre-release

Added

  • Scheduling: support for registering a payment step. See doc for details/instructions.

Changed

  • Core: NablaClient.authenticate is replaced by NablaClient.setCurrentUserOrThrow and NablaClient.clearCurrentUser. provideAuthTokens is set during NablaClient.initialize.

Fixed

Versions

1.0.0-alpha14

23 Feb 14:29
Compare
Choose a tag to compare
1.0.0-alpha14 Pre-release
Pre-release

[1.0.0-alpha14] - 2023-02-22

Added

  • Messaging Core: Added a new Response object returned by watchers. It contains metadata about the freshness of the data returned, allowing the caller to know if the data comes from cache or is fresh and if a background refresh is in progress.

Changed

  • Messaging Core: watchConversation success callback is now called with a Response<Conversation>, NablaError>.
  • Messaging Core: watchItemsOfConversation success callback is now called with a Response<PaginatedList<ConversationItem>, NablaError>.
  • Messaging Core: watchConversations success callback is now called with a Response<PaginatedList<Conversation>> NablaError>.

Fixed

  • Core: fixed a crash that occurred on iOS when authenticating a different user or the same user multiple times.
  • Messaging Core: Fixed createConversationWithMessage not correctly setting providerIds on Android.

Versions

1.0.0-alpha13

30 Jan 13:48
Compare
Choose a tag to compare
1.0.0-alpha13 Pre-release
Pre-release

[1.0.0-alpha13] - 2023-01-30

Added

  • A new onAppointmentSelected property is available in NablaAppointmentListView component and should be provided to redirect to the appointment detail screen (NablaSchedulingUI.navigateToAppointmentDetailScreen(appointmentId)).
    (This callback will only be used on iOS and the navigation will work as expected on Android)

Changed

  • NablaSchedulingClient.openScheduleAppointmentScreen() has been renamed to NablaSchedulingUI.navigateToScheduleAppointmentScreen() in the NablaScheduling package.

Fixed

Versions

1.0.0-alpha12

02 Jan 15:56
Compare
Choose a tag to compare
1.0.0-alpha12 Pre-release
Pre-release

[1.0.0-alpha12] - 2023-01-02

Versions

1.0.0-alpha11

14 Dec 16:48
Compare
Choose a tag to compare
1.0.0-alpha11 Pre-release
Pre-release

[1.0.0-alpha11] - 2022-12-14

Added

Changed

  • Messaging Core: Renamed createDraftConversation to startConversation. It keeps the behavior of creating the conversation lazily when the patient sends the first message.
  • Messaging Core: createConversation has been renamed createConversationWithMessage and now has a required message argument. It should be used to start a conversation on behalf of the patient with a first message from them.

Fixed

  • Fixed some cases in MessagingCore where the success callback was called too in addition to the error callback when the method fails.

Versions