Skip to content

fix: make MappingProperty.type field optional to handle nested fields mappings#245

Open
adrianlzt wants to merge 1 commit intoelastic:mainfrom
datadope-io:fix/optional-mapping-type-field
Open

fix: make MappingProperty.type field optional to handle nested fields mappings#245
adrianlzt wants to merge 1 commit intoelastic:mainfrom
datadope-io:fix/optional-mapping-type-field

Conversation

@adrianlzt
Copy link
Copy Markdown

Fix #185

@xdm67x
Copy link
Copy Markdown

xdm67x commented Feb 26, 2026

Any idea when this fix will be merged?

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.

get_mappings tool fails with "error decoding response body" when nested type is omitted in properties

2 participants