As previously discussed in several places (e.g.
STRIPES-172, STRIPES-452), we have a lot of near-duplicate code in ui-users and ui-items, the first two modules that are based on searching, listing, viewing and editing records of different types. Now with UIREQ-1, UIREQ-2, UIREQ-3, UIREQ-8 and maybe others, we are in danger of creating a third nearly-the-same-but-not-quite module by copy-pasting and editing the result.
This is probably the right time to take the concrete lessons of ui-users and ui-items, and use them to create a general framework for such modules – and then to make ui-requests another instance of that general framework. (We did much the same for the modules' settings pages in
STRIPES-343, which gave us the <Settings> component which now also underlies ui-organization and other modules.)
This is potentially a wide-ranging task. It will need some careful design, some refactoring in ui-users and ui-items, possibly some improvements in test-suite coverage, and new documentation. The good news is that, once done, it should make many of the ui-requests issues trivial to implement.