-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[Discover] <FieldIcon/> usage is inconsistent #124017
Copy link
Copy link
Closed
Labels
:DataDiscovery/fix-it-weekFeature:DiscoverDiscover ApplicationDiscover ApplicationTeam:DataDiscoveryDiscover, search (data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. t//Discover, search (data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. t//bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experienceimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.
Metadata
Metadata
Assignees
Labels
:DataDiscovery/fix-it-weekFeature:DiscoverDiscover ApplicationDiscover ApplicationTeam:DataDiscoveryDiscover, search (data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. t//Discover, search (data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. t//bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experienceimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Kibana version: Main (8.1)
Describe the bug:
Looks like logic for extracting
typefrom afieldfor<FieldIcon/>is different in different places in discover.For example, discover's document table always displays string fields icons as string, but the field list displays an underlying es type (e.g.
versionortext)Steps to reproduce:
versionortextExpected behavior:
They should be displayed in the same manner in different places.
Screenshots (if relevant):
Any additional context:
Noticed in: #123739