Clarify query string action to matching route map

I’m trying to add a query parameter to one of my routes, using:

<Link to={{type: 'SEARCH', payload: {find: this.state.findValue /* string */}}}> Blah </Link>

With the route

{
  SEARCH: '/search',
}

Ive also tried adding the query field, dased on these docs:

<Link to={{type: 'SEARCH', payload:  {find: this.state.findValue /* string */}}}> Blah </Link>

As well as adding a dynamic field to my route map:

{
  SEARCH: '/search/:find',
}

But I can’t seem to get RFR to change my query string for me. I have to do something like

{
  SEARCH: '/search?find=:find
}

To get the query string to show up at all. But from your live example it seems that I shouldn’t need to manually code the query string in the route. In addition, I never find my query at store.getState().location.query after I click my link.

So with that all said, what is the proper mapping between what you supply to Link to={…} and what your route looks like in your routes map, in order RFR create the query string for you?

[Maushundb]

Not yet, it seems that the SSR is getting it right, but the client isn’t for some reason (Turning off JS on the page in dev makes it work!). I’m certainly closer, but I’ll get back to it in the morning. I’m using your demo app as a base if it makes anything come to mind. Thanks for the fast help so far, stoked to get this working!

[faceyspacey]

oh shit. i totally i forgot about that. my bad. i’ll add it now.