112 unknown group when using additional spring configuration metadatajson#119
Merged
nandorholozsnyak merged 2 commits intoAug 20, 2025
Conversation
…ration-metadata-javers.json
…hen-using-additional-spring-configuration-metadatajson
This file contains hidden or 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
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.
Fix: "Unknown group" When Using
additional-spring-configuration-metadata.jsonfor Custom GroupsSummary
This PR addresses an issue where custom groups defined in
additional-spring-configuration-metadata.jsonwere not recognized correctly, resulting in properties being assigned to an "Unknown group" in the generated documentation. The fix ensures that groups and properties are properly linked when thetypeandsourceTypefields are set consistently.Details
additional-spring-configuration-metadata.jsonwith matchingtypeandsourceTypefields.typeandsourceTypefields.How to Use
To ensure your custom groups and properties are recognized:
typeandsourceTypefor your group.sourceTypeto each property belonging to the group.Example:
{ "groups": [ { "name": "audit.javers", "type": "audit.JaversProperties", "sourceType": "audit.JaversProperties" } ], "properties": [ { "name": "audit.javers.enabled", "type": "java.lang.Boolean", "defaultValue": true, "description": "Whether Javers audit logging is enabled.", "sourceType": "audit.JaversProperties" } ] }