fix(core): Property's type should be nullable #117
Merged
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.
Pull Request: Support Optional
type
Field in Spring Boot Metadata & Template CleanupSummary
This PR implements support for configuration properties without a
type
field, as allowed by the Spring Boot metadata specification. It also refines Handlebars templates to prevent extra blank lines in generated documentation.Changes
Core Logic
type
field is now optional in property metadata parsing and grouping.type
values gracefully.Templates
.hbs
files) for Markdown, HTML, and AsciiDoc now use the tilde (~
) inif
statements to suppress unwanted whitespace.type
field is now whitespace-safe.Tests
type
.Motivation
Spring Boot does not require the
type
field for configuration properties. This change ensures compatibility and prevents errors for such cases. Template improvements result in cleaner, more predictable documentation output.Notes
type
field.