Fix for record component annotations on fields with JsonProperty annotations #4795
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
frantuma
approved these changes
Dec 9, 2024
|
Thanks! |
richard-lindsay
deleted the
bug/support-json-properties-on-record-component-annotations
branch
ndwlocatieservices
added a commit
to ndwnu/nls-accessibility-map
that referenced
this pull request
Dec 19, 2024
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [nu.ndw.nls.locationdataissuesapi:client-feign](https://dev.azure.com/ndwnu/NLS/_git/nls-location-data-issues) ([source](https://dev.azure.com/ndwnu/NLS/_git/nls-location-data-issues)) | compile | patch | `1.0.14` -> `1.0.15` | | nu.ndw.nls.geojson.geometry:specification | | patch | `1.3.5` -> `1.3.8` | | nu.ndw.nls.geojson.geometry:specification-open-api-config | | patch | `1.3.5` -> `1.3.8` | | nu.ndw.nls.geojson.geometry:geometry-model | compile | patch | `1.3.5` -> `1.3.8` | | nu.ndw.nls.geojson.geometry:specification | compile | patch | `1.3.5` -> `1.3.8` | | nu.ndw.nls.geojson.geometry:geometry-jts | compile | patch | `1.3.5` -> `1.3.8` | | [nu.ndw.nls:routing-map-matcher-library](https://github.com/ndwnu/nls-routing-map-matcher) | compile | minor | `13.2.4` -> `13.3.0` | | [io.swagger.core.v3:swagger-annotations](https://github.com/swagger-api/swagger-core) | compile | patch | `2.2.26` -> `2.2.27` | --- ### Release Notes <details> <summary>swagger-api/swagger-core (io.swagger.core.v3:swagger-annotations)</summary> ### [`v2.2.27`](https://github.com/swagger-api/swagger-core/releases/tag/v2.2.27): Swagger-core 2.2.27 released! [Compare Source](swagger-api/swagger-core@v2.2.26...v2.2.27) - fix: swagger-api/swagger-ui#10220 ([#​4806](swagger-api/swagger-core#4806)) - Fix for record component annotations on fields with JsonProperty annotations ([#​4795](swagger-api/swagger-core#4795)) - Fix java.lang.NullPointerException and remove stack trace output from ModelResolver ([#​4793](swagger-api/swagger-core#4793)) - Move applySchemaResolution check to a method ([#​4791](swagger-api/swagger-core#4791)) - feat(gradle-plugin): enable lazy evaluation, implicit task dependencies and fixing `setEncoding` ([#​4761](swagger-api/swagger-core#4761)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or PR is renamed to start with "rebase!". 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for record classes with
@JsonPropertyannotations that do not match the field names when getting the component annotations.When these two differ a NoSuchMethodException is throw. Instead access the declared method using the name of the primary member.