RFC 7515, Section 2 states:

JWS Payload
The sequence of octets to be secured -- a.k.a. the message. The
payload can contain an arbitrary sequence of octets.

This is reinforced by the example shown in Appendix A4 using a payload of the string literal Payload.

As

The tool generates code that causes PMD UnnecessaryModifier warnings for generated enums .
(https://pmd.github.io/latest/pmd_rules_java_codestyle.html#unnecessarymodifier)
It might make sense to change the autogenerated code not to have

    private SomeEnum(String value) {
        this.value = value;
    }

but

SomeEnum(String value) {
    this.value = value;
}

I can't find the documentation in this repo.

In this page https://immutables.github.io/apt.html#intellij-idea, after the configuration description, a note should be added stating that the generated folders ("generated-sources/annotations" and "generated-test-sources/test-annotations") should then be marked as "Generated Sources Root".

I think the instructions and code examples could be more specific about the fact that readValue is reified and it needs to be imported in order for the mapper to work.

import com.fasterxml.jackson.module.kotlin.readValue

I spent some time finding an issue with my code because I did not take wildcard import instruction literally. I just imported jacksonObjectMapper from the kotlin module. :

When I use the gradle plugin with Gradle 6, I get the following deprecation warning.

> Task :generateTypeScript
Running TypeScriptGenerator version 2.21.588
The compile configuration has been deprecated for resolution. This will fail with an error in Gradle 7.0. Please resolve the compileClasspath configuration instead. Consult the upgrading guide for further information: https://docs.grad

I see that x-server-raw-response is available to expose the underlying to users, allowing deeper customization of response.

I was wondering if it's possible to expose a similar interface for request as well? So that we can utilize some predefined functions by akka-http. For example, extractClientIP.

Not a huge deal and is blocking anything, since we can simply replicate all these funct

It's not clear fromt he current documentation the operator precedence (pipe, logical, arithmetic, etc)

I would be great to have a documentation page backed by tests on query-tests.yaml.