The route matching logic should be revisited (index.js), works for now, hope it didn't break the search path logic

Not to worry, the search path logic was already not working, as documented in

Initial implementation of single user view done.

Implemented full view of selected user.

Comments:

• MultiColumnList was forked and the fork specialized for this view (adding user id to input and onClick handler to select a user by id)

• Fines info still hard-coded (not sure they are present in the backend yet)

• The route matching logic should be revisited (index.js), works for now, hope it didn't break the search path logic

• The full view pane is (perhaps confusingly) empty until a user is selected by clicking a line in the users table

Discussed with Mike how this piece of development will align with

We talked about single-keyword search that would do a full word match on any field of the record. So “john” or “wall” would both match the imaginary (all fields made up) record (<name>john doe</name><address>123 wall st., NYC</address>.