fix: remove the resolvedMapLocation from API#2378
Conversation
| @Schema(hidden = true) | ||
| @JsonInclude(JsonInclude.Include.NON_EMPTY) |
There was a problem hiding this comment.
This is only a partial hotfix, since for routing models, the field will be non-empty and thus it will be sent in the JSON payload to the client side.
Doing the full split means handling this in the REST API, both in the solver-service and the platform.
Another option is reverting the original change.
mswiderski
left a comment
mswiderski
left a comment
There was a problem hiding this comment.
I'd go with this as quick fix to make sure this is not "advertised" via open api and then be refactored down the line.
|
I am ok with hiding it or removing it completely for now, as this is not an urgent feature. |
|
|
Closing in favor of #2380 and https://github.com/TimefoldAI/timefold-solver-enterprise/pull/702. |
3 participants
The
resolvedMapLocationleaked into the API, where it does not belog.