This repository has been archived by the owner on Apr 30, 2024. It is now read-only.
Releases: nabla/nabla-react-native
Releases · nabla/nabla-react-native
1.1.3
1.1.2
1.1.0
1.0.1
1.0.0
1.0.0-alpha15
Added
- Scheduling: support for registering a payment step. See doc for details/instructions.
Changed
- Core:
NablaClient.authenticate
is replaced byNablaClient.setCurrentUserOrThrow
andNablaClient.clearCurrentUser
.provideAuthTokens
is set duringNablaClient.initialize
.
Fixed
Versions
- Android:
1.0.0-alpha25
- iOS:
1.0.0-alpha33
1.0.0-alpha14
[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 aResponse<Conversation>, NablaError>
. - Messaging Core:
watchItemsOfConversation
success callback is now called with aResponse<PaginatedList<ConversationItem>, NablaError>
. - Messaging Core:
watchConversations
success callback is now called with aResponse<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
- Android:
1.0.0-alpha24
- iOS:
1.0.0-alpha32
1.0.0-alpha13
[1.0.0-alpha13] - 2023-01-30
Added
- A new
onAppointmentSelected
property is available inNablaAppointmentListView
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 toNablaSchedulingUI.navigateToScheduleAppointmentScreen()
in the NablaScheduling package.
Fixed
Versions
- Android:
1.0.0-alpha22
- iOS:
1.0.0-alpha30
1.0.0-alpha12
1.0.0-alpha11
[1.0.0-alpha11] - 2022-12-14
Added
Changed
- Messaging Core: Renamed
createDraftConversation
tostartConversation
. It keeps the behavior of creating the conversation lazily when the patient sends the first message. - Messaging Core:
createConversation
has been renamedcreateConversationWithMessage
and now has a requiredmessage
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
- Android:
1.0.0-alpha21
- iOS:
1.0.0-alpha28