Jan Martiska

Done, this will be fixed in 1.7.1 and 2.0.0

I think that adding multiple fields should be possible, but shouldn't this work even without the annotation? Why should we require it? Even if we decide that we need an...

Oh I see. JPA has something similar, but you need two annotations - `@Embeddable` on the class that you "include" into an entity - `@Embedded` where you perform the embedding,...

OK, I'll take care of the backport and releasing a 1.8.x build of SmallRye GraphQL

We talked about this together on Zulip, so just briefly the next steps: - Support the `graphql-ws` protocol too - Support configuring via `CLIENT_NAME/mp-graphql/init-payload/KEY=VALUE` properties Also please update the relevant...

@t1, I'm afraid that supporting 1.8.x by the feature pack isn't possible because of a compatibility mismatch: - WildFly 23-26 has Jandex 2 and javax namespace - WildFly 27 will...

Might be related to https://github.com/smallrye/smallrye-graphql/issues/1506, the symptom is the same

The `payload` field is optional, hence the question mark behind it in the protocol specification. Therefore saying that "graphql-transport-ws is not working" isn't correct - we only have a limitation...

Do you have any particular idea what the API should look like? How will the application define the payload items?

It might need a way to specify the values dynamically because they might change over time, in which case a simple configuration property wouldn't work, but rather an SPI that...