Validate barcode uniqueness asynchronously

Description

As we do for username uniqueness in ui-users

At present, we go right ahead and submit new records whose barcodes are not unique, and get back a 400 Bad Request with body "Barcodes must be unique, 12 is already assigned to another item" (which admittedly is nice and explicit.) But we shouldn't even submit such records.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Mike Taylor June 24, 2017 at 1:02 AM

Fixed in https://github.com/folio-org/ui-items/commit/f9505c9373705f12e621fae9571cc55ac9836b3c

This uses the okapi prop passed into the top-level components, rather than Okapi parameters pulled in from stripes-loader like the async "username" uniqueness validation in ui-users. We should backport this cleaner method to ui-users.

Done

Details

Assignee

Reporter

Labels

Priority

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created June 22, 2017 at 12:33 AM
Updated July 11, 2017 at 12:51 PM
Resolved June 24, 2017 at 1:02 AM
TestRail: Cases
TestRail: Runs