v3.x missing feature - configuring the schema encoder

[Sterta]

Before 3.x it was possible for example to do something like this:

typealias SchemaEncoder = (type: SchemaType) -> String?

    encoding {
        schemaEncoder { type ->
            when (type.javaType) {
                ByteArrayWrapper::class.java -> jssJson.encodeToSchema(
                    serializer = ByteArrayWrapperSerializer
                )

                UUID::class.java -> jssJson.encodeToSchema(
                  serializer = UUIDSerializer
                )
                OffsetDateTime::class.java -> jssJson.encodeToSchema(
                    serializer = OffsetDateTimeSerializer
                )

                else -> {
                    jssJson.encodeToSchema(
                        serializer = serializer(type)
                    )
                }
            }
        }
        schemaDefinitionsField = "definitions"
    }

For the example encoder it is possible with 3.x.

I couldn't find a way to implement the schema encoder example with 3.x.

Is this not possible anymore, or is their a way?

If not, is it possible to add this functionality again?

[SMILEY4]

The "old" schema generator was replaced with a completely new one which works a quite bit different now. You can customize this new schema generator, some information here.

You can then for example:

• customize the general schema generation steps, to e.g. handle swagger or jackson annotations (more info here)
• generate a specific type as another given type via type redirects
• completly customize the input data for the schema generation via custom type processors

there is currently also an open issue about custom schema for LocalDateTime that might be relevant.

I hope these links are helpful enough. I'm still working on the new schema generator and the wiki, so if you encounter any questions or issues, please let me know.