Skip to content
This repository has been archived by the owner on May 8, 2019. It is now read-only.

Releases: onfido/onfido-sdk-core

1.1.0

04 May 15:33
Compare
Choose a tag to compare
1.1.0 Pre-release
Pre-release

Changed

  • Internal: Remove unused getUserMedia code
  • Internal: Remove capture callbacks. These are now part of SDK UI.

1.0.1

04 May 15:34
Compare
Choose a tag to compare

Changed

  • Internal: Pass React component props to selectors.
  • Public: Support capturing the reverse side of documents..

0.7.1

11 Jan 15:13
Compare
Choose a tag to compare

Changed

  • Internal: Removed lodash, 50KB reduced from minified JS bundle file.
  • Update the URL of the websockets server.

Added

  • Pass websockets URL to connect. Default to production.

0.7.0

05 Dec 10:23
Compare
Choose a tag to compare

Changed

  • Events are only dispatched when condition has been met and also changed. Before events were getting dispatched every time the condition was met and the store changed (even if the condition hadn't changed).
  • The events '(document|face)Capture' now gets called only when the capture has been confirmed.

0.6.0

28 Sep 12:41
Compare
Choose a tag to compare

Changed

  • The action validCapture has been changed to validateCapture.
  • The payload of the action createCapture has changed from {...data: object} to {...capture: object}.
  • All selectors have now been changed from having identical pairs of selectors for both document and face to be capture type agnostic selectors, meaning they are now mapped into the captures hash which includes all capture types as keys.
  • faceSelector|documentSelector:[Object] changed to validCaptures:{string:[Object]}
  • documentCaptured|faceCaptured:boolean changed to isThereAValidCapture:{string:boolean}.
  • faceValidAndConfirmed|documentValidAndConfirmed:boolean changed to isThereAValidAndConfirmedCapture:{string:boolean}

Added

  • The action validateCapture now also changes the value in the capture of the property processed to true whenever the action is called.
  • The action createCapture can now accept a new optional parameter called maxCaptures: int, which determines how many captures are stored. The default of maxCaptures is 3.
  • The payload of the action validateCapture can have an extra parameter called valid: boolean which is optional and defaults to true, this can be used to invalidate the capture.
  • There is a new selector called unprocessedCaptures:{string:[Capture]} which returns a list of captures which have not yet been been validated/invalidated for each capture type.
  • There is a new selector hasUnprocessedCaptures:{string:boolean} which returns a boolean on whether there are unprocessed Captures for each capture type.
  • There is a new selector areAllCapturesInvalid:{string:boolean} which returns a boolean on whether all of its captures are invalid for each capture type.
  • Events are now sent for any capture type.
  • The selector allCaptured is now capture type agnostic, but still backwards compatible.

0.5.0

16 Sep 09:31
Compare
Choose a tag to compare

Added

  • the action CAPTURE_CONFIRM is now available, it expects a payload.data.id for determining which capture to confirm.

Changed

  • selector allCaptured and consequentially event complete are now only triggered when the captures are both validated and confirmed.

0.4.1

28 Jul 18:19
Compare
Choose a tag to compare

Path:

  1. Fix null exception when calling getCaptures()

0.4

28 Jul 18:04
Compare
Choose a tag to compare
0.4

Breaking changes:

  1. Refactored the document and facial captures to one capture endpoint