Fix top level field mappings issue, use dynamic: 'false' instead of dynamic: false#226988
Conversation
|
Pinging @elastic/kibana-core (Team:Core) |
dynamic: property on index mappings
| * *never* use `dynamic: 'true'`. | ||
| */ | ||
| dynamic?: false | 'strict'; | ||
| dynamic?: MappingDynamicMapping; |
There was a problem hiding this comment.
This type is defined as:
export type MappingDynamicMapping = boolean | 'strict' | 'runtime' | 'true' | 'false';
And we want to avoid anyone using boolean and 'true' not sure if 'runtime' would even work with saved objects.
So I would maybe rather type it as 'false' | 'strict'
755b88b to
05711a7
Compare
ed69995 to
32d4b40
Compare
32d4b40 to
c15e88e
Compare
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Public APIs missing exports
History
cc @gsoldevila |
Summary
Closes https://github.com/elastic/kibana-team/issues/1802
The PR aims at aligning the in-memory representation with the one coming from ES mappings, to prevent such discrepancies.