Break out core search/sort functionality into re-usable utility component
Description
Environment
None
Potential Workaround
None
blocks
is blocked by
Checklist
hideTestRail: Results
Activity
Show:
Mike Taylor October 31, 2017 at 1:48 AM
I've made a new issue for the ongoing work, . This one can be closed, now that the primary decomposition of the monolithic ui-users is done.
Mike Taylor October 31, 2017 at 12:22 AM
The merge is done. I will check the results first thing in the morning.
Mike Taylor October 31, 2017 at 12:10 AM
I am going to go ahead and do a "speculative merge" into master so that I can get the integration tests run against the new branch – I have never, ever, got them to run successfully on my development box. If that fails, then at this time of night any consequences should be minor, and I'll be able to back out the merge tomorrow morning before it affects anyone much. Hopefully that won't be necessary.
Mike Taylor October 31, 2017 at 12:08 AM
Lots more pithering, moving bits and pieces around.
Mike Taylor October 30, 2017 at 9:16 PM
Filed "Silent no-op when adding an address with unrecognised country" as .
Done
Created October 19, 2017 at 11:06 AM
Updated November 3, 2017 at 7:04 PM
Resolved October 31, 2017 at 1:49 AM
TestRail: Cases
TestRail: Runs
As the first stage in STRIPES-462, I need to break the large
Users.jscomponent apart into two:lib/SearchAndSort/SearchAndSort.js, which contains the generic and configurable code for presenting and operating such a module, and the stub ofUsers.jswhich should contain only those parts of the code that are specific to users.The latter will include much of the manifest (though the utility component may be able handle the local resource used for the result-count, and the communication with the notes module). Resources and mutators will need to be passed into the generic module, along with numerous callbacks such as the row formatter and the function for viewing a single record in detail.