JTS support for KSP codegen

[Tocktock]

Important Notice

Thank you for opening an issue! As noted in the [README](https://github.com/OpenFeign/querydsl?tab=readme-ov-file#i-need-feature-x-or-bug-z-fixed), please be aware that I can only work on new features or bug fixes when they are sponsored. Due to balancing this project with other professional and personal commitments, the time I can dedicate here is very limited.

Therefore, in order for this issue to be addressed, contributors must be willing to take ownership and provide the necessary work.

• I am willing to put in the work and submit a PR to resolve this issue.

Is your feature request related to a problem? Please describe.
Yes. When generating org.locationtech.jts.geom.Geometry fields, the KSP code generator does not produce the corresponding QClass.

Describe the solution you'd like
Add support in the KSP code generator for JTS types.

Describe alternatives you've considered
Currently, the only alternative is to use kapt.

[github-actions]

This issue has been automatically closed because the author did not indicate they are willing to put in the effort needed to resolve it.

[github-actions]

This issue has been automatically closed because the author did not indicate they are willing to put in the effort needed to resolve it.

[github-actions]

This issue has been automatically closed because the author did not indicate they are willing to put in the effort needed to resolve it.

[Tocktock]

i think bot is broken

[IceBlizz6]

Hey, sorry for the broken bot.
Just wanted to let you know that i've seen this and will try to find some time this week to work on it.
If you can then please post an entity class that i can use to test with.
if you are currently use kapt then you could also include the Q class output from that, which i will use to compare and confirm that the patch works.

Thank you for taking the time to post this issue!

[Tocktock]

@IceBlizz6

Thank you for the follow-up, and for looking into this. As requested, here’s a minimal reproducible example using kapt. It includes only the ID and a JTS Geometry field. The kapt-generated Q type resolves to the expected JTSGeometryPath, which you can compare against the KSP output.

Entity (Kotlin)

package com.example.spatial

import jakarta.persistence.*
import org.locationtech.jts.geom.Geometry

@Entity
@Table(name = "order_detail")
class OrderDetailV3(
    @Id @GeneratedValue(strategy = GenerationType.IDENTITY)
    val id: Long = 0,
    val departureGeo: Geometry? = null
)

Q class (Java, kapt output – essential lines)

package com.example.spatial;

import static com.querydsl.core.types.PathMetadataFactory.*;
import com.querydsl.core.annotations.Generated;
import com.querydsl.core.types.Path;
import com.querydsl.core.types.PathMetadata;
import com.querydsl.core.types.dsl.*;

@SuppressWarnings("this-escape")
@Generated("com.querydsl.codegen.DefaultEntitySerializer")
public class QOrderDetailV3 extends EntityPathBase<OrderDetailV3> {

    public static final QOrderDetailV3 orderDetailV3 = new QOrderDetailV3("orderDetailV3");

    public final NumberPath<Long> id = createNumber("id", Long.class);

    // JTS Geometry → expected Querydsl Spatial path
    public final com.querydsl.spatial.locationtech.jts.JTSGeometryPath departureGeo =
        new com.querydsl.spatial.locationtech.jts.JTSGeometryPath(forProperty("departureGeo"));

    public QOrderDetailV3(String variable) { super(OrderDetailV3.class, forVariable(variable)); }
    public QOrderDetailV3(Path<? extends OrderDetailV3> path) { super(path.getType(), path.getMetadata()); }
    public QOrderDetailV3(PathMetadata metadata) { super(OrderDetailV3.class, metadata); }
}

Gradle (relevant entries)

dependencies {
  implementation "io.github.openfeign.querydsl:querydsl-jpa:7.0"
  implementation "io.github.openfeign.querydsl:querydsl-spatial:7.0"
  kapt         "io.github.openfeign.querydsl:querydsl-apt:7.0:jakarta"
  implementation "org.locationtech.jts:jts-core:1.19.0" // for org.locationtech.jts.geom.Geometry
}

Thanks again for your time!