Jason Pickens

Fixes #635 Logs the error from the query if it cause the props to be null. This doesn't seem particularly great but it does what the other error case does....

Certain errors will cause the props to be `null`. For some reason `renderElement` assumes that if the props are `null` then it is because there is no `render` method or...

Fixes #373

graphql-js removed support for positional arguments in the call to `graphql`. It must now be a single `GraphQLArgs` object. Passing it as positional arguments (i.e. schema first meaning that schema...

When context-applied is enabled it breaks the following: ``` import scala.language.experimental.macros import scala.reflect.macros.blackbox trait F[A] object MacroImpl { def myMacroImpl(c: blackbox.Context)()(bob: c.Expr[F[_]]): c.Expr[Unit] = { import c.universe._ c.Expr[Unit](q"""()""") } }...

Fixes #1061

Unable to use Redirect as a component

1

It is a little hard for me to nail down exactly what the problem is since I am using Scala.js with [ScalablyTyped](https://scalablytyped.org/docs/readme.html) bindings for found but this is what I...

Doesn't look like custom parameter prefixes are supported

1

I was trying to create a custom parameter prefix as documented in https://github.com/pillarjs/path-to-regexp?tab=readme-ov-file#custom-prefix-and-suffix but it doesn't seem to work. It would be nice for doing `foo{/:path}?` which would match `foo`...

The basic example has one of the children as: ``` new Redirect({ from: 'baz', to: '/foo', }), ``` If this is converted to TypeScript then it does not type check....

Fixes #1057 I'm not sure if this is the idea solution. It maintains the same runtime behaviour but of course there is a breaking change in the types. Alternatively we...