Rüdiger zu Dohna
Rüdiger zu Dohna
I found some smaller issues about the dynamic vs. typesafe client APIs, I think we should talk about. We should consider to: * Merge `Error` and `GraphQlClientError` into new `common.api`...
See #339 The typesafe client supports aliases (see #611/#722). Now we could add them to the generator.
see #627 and #339
If an input parameter type already ends with `Input`, e.g. `SuperHeroInput`, the generated schema shouldn't repeat it to become `SuperHeroInputInput`.
And support `@JsonbProperty` in addition to `@Name` annotations. This is a prerequisite of #316.
The GraphiQL-UI doesn't work on, e.g., WildFly, because the application runs on a sub-path, e.g. `https://hostname/appname/graphql` but the `render.js` file defines the api path to be just `/graphql`. If this...
I added [power-annotations](https://github.com/t1/power-annotations) to the typesafe client as a PoC. There are two tests that show using a [Stereotype](https://github.com/t1/smallrye-graphql/blob/power-annotations/client/implementation/src/test/java/test/unit/StereotypeBehavior.java) and a [Mixin](https://github.com/t1/smallrye-graphql/blob/power-annotations/client/implementation/src/test/java/test/unit/MixinBehavior.java). Maybe you can take a look? It's in...
Many BeanValidation annotations could be mapped to `@constraint` directives that are specified, e.g., by [graphql-constraint-directive](https://github.com/confuser/graphql-constraint-directive). This would allow clients to validate user input directly in the frontend... even while typing......
Just a few, minor fixes.
When we redeploy a `war` on a WildFly with an update to the `microprofile-config.properties` concerning MP GraphQL, e.g. `mp.graphql.showErrorMessage`, then the changes don't get applied; it needs a full restart...