Confusing API of route.action

[hikarino-my]

Current routing API as below is quite misleading, because React users think route.action accepts React Component, but actually doesn't.

const toplevelRoutes = Rocon.Path()
  .route("foo", (route) => route.action(() => <p>This is foo</p>));

Suggestion

there's several options to solve this.

1. Add note to the Document on this page.
   AFAIK, this behavior isn't mentioned nor warned in the document.
   Or if it is, it should be more emphasized.
2. Add another API that will accept React Component.
3. Make route.action accept React Component
   I'm not sure these options are possible since this library is designed not only for React.
   Though adding some React friendly wrapper API that'll accept it and make React users use that API will be enough.
4. Detect it is React Component or not before or during runtime before react warns it
   I don't think this is possible

[uhyo]

@hikarinotomadoi
Thank you for reporting this!
We fixed this in v1.2.2. With that version, you can pass a React component as action.