Skip to content

chore: add escape hatch for SolverConfig in Quarkus build time#2156

Open
Christopher-Chianelli wants to merge 1 commit intoTimefoldAI:mainfrom
Christopher-Chianelli:fix/quarkus-null-value-range-provider-id
Open

chore: add escape hatch for SolverConfig in Quarkus build time#2156
Christopher-Chianelli wants to merge 1 commit intoTimefoldAI:mainfrom
Christopher-Chianelli:fix/quarkus-null-value-range-provider-id

Conversation

@Christopher-Chianelli
Copy link
Contributor

Due to what I assume to be classloader shenanigans, the generated Gizmo classes cannot access annotations on fields/methods at Quarkus build time.

An escape hatch was added to SolverConfig for those users that need to build a Solver or related components at Quarkus build time.

Due to what I assume to be classloader shenanigans, the generated
Gizmo classes cannot access annotations on fields/methods at
Quarkus build time.

An escape hatch was added to SolverConfig for those users that need
to build a Solver or related components at Quarkus build time.
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 2, 2026

Copy link
Collaborator

@triceo triceo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed on Slack, we should make sure the SDK can access the constraint metamodel through the build item which already exists.

The build item probably needs to do the same hack that the PR already uses. The benefit is though that the build item need not do this publicly and therefore the method on solver config need not exist.

(Arguably, we should do something similar with the gizmo stuff on solver config as well. We have access to internals, we should just push this information through wherever we need this, without bothering the user with this nasty impl detail.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants