(I think this is probably a stripes-components bug, but I will move it to a different project if it turns out that I am doing something dumb in my invocation.)
As noted in UISE-19, the ui-search module is now correctly fetching the six sample records from Heikki's mock module. But the records don't display: for some reason, <MultiColumnList> doesn't seem to re-render the embedded <MCLRenderer> when the records appear, so we're left with the "No results found. Please check your filters" message from the initial render.
This might be a reaction to some key field not being in the schema ... or something.
Aha – it's now apparent that https://github.com/folio-org/stripes-components/blob/master/lib/MultiColumnList/MCLRenderer.js#L618 is throwing an exception, because it's looking up the value of the field barcode, which is not defined, then trying to invoke toString on the result. So this is caused simply by my invocation of <SearchAndSort> (and hence its invocation of <MultiColumnList>) trying to display a field that is not in the schema for the relevant records.
I can fix that in the invocation of course, so I will move this issue into UISE and rename it. But I wonder whether <MultiColumnList> ought to do something more polite when asked to render a non-existent field?
(I think this is probably a stripes-components bug, but I will move it to a different project if it turns out that I am doing something dumb in my invocation.)
As noted in UISE-19, the ui-search module is now correctly fetching the six sample records from Heikki's mock module. But the records don't display: for some reason,
<MultiColumnList>doesn't seem to re-render the embedded<MCLRenderer>when the records appear, so we're left with the "No results found. Please check your filters" message from the initial render.This might be a reaction to some key field not being in the schema ... or something.