312 react router

[michael-duren]

React router first pass.

• Refactored TsmlUi.tsx removed state and moved it to StateContext, this is not necessary and can be changed back.
• Installed react-router-dom, updated Link to use react routers Link component and created useEffect in TsmlUI.tsx to listen for changes to location, and update state accordingly
• 5 tests currently fail, I had to update some of the helper function signatures to use react router. I wanted to get eyes on this before updating any tests.
• There is an issue with the query params in the URL not being updated when filtering meetings from the Controls.tsx component. The UI updates to show the filtered output, but URL does not include query string.

[netlify[bot]]

❌ Deploy Preview for tsml-ui failed.

Name	Link
🔨 Latest commit	49f1ff4437a332a23011983b05ac89e5b8e528ed
🔍 Latest deploy log	https://app.netlify.com/sites/tsml-ui/deploys/653ec5cf0e36330008734f2a

[michael-duren]

I am going to redo this.

[joshreisner]

hey this looks good @michael-duren ! i did notice the same issues you did about the tests about the helper functions and the URL not updating.

so we have this input key in state, what if we got rid of that and instead started using useSearchParams as the source of truth for that?

  input: {
    distance: string[];
    latitude?: number;
    longitude?: number;
    meeting?: string;
    mode: 'search' | 'location' | 'me';
    region: string[];
    search?: string;
    time: TSMLReactConfig['times'];
    type: string[];
    view: 'table' | 'map';
    weekday: TSMLReactConfig['weekdays'];
  };

[michael-duren]

I like this idea @joshreisner. I'm going to give another work through this weekend