Explicit namespaces for esQuery and esKuery#57172
Conversation
|
Pinging @elastic/kibana-app-arch (Team:AppArch) |
|
@elasticmachine merge upstream |
…izozom/kibana into newplatform/data/kuery-query-namespace
pgayvallet
left a comment
There was a problem hiding this comment.
LGTM for platform changes
|
SIEM is not marked as code owners (and I don;t know your GITHUB handle), so you didn't get an automatic notification, but I wanted to ket you know about some changes in this PR:
|
…ata/kuery-query-namespace
lukeelmers
left a comment
There was a problem hiding this comment.
This feels SO much cleaner than what we had before! Thanks for taking the time to do this @lizozom ... Code all LGTM
| export type JsonValue = null | boolean | number | string | JsonObject | JsonArray; | ||
|
|
||
| export interface JsonObject { | ||
| [key: string]: JsonValue; | ||
| } | ||
|
|
||
| // eslint-disable-next-line @typescript-eslint/no-empty-interface | ||
| export interface JsonArray extends Array<JsonValue> {} |
There was a problem hiding this comment.
Would it make more sense to put this in packages/kbn-utility-types?
I could go either way, but this does feel like a pretty basic TS interface that I could see folks reaching for a lot, and kbn-utility-types seems designed to address this use case more than kibana_utils.
…kuery-query-namespace
| import { Dispatch } from 'redux'; | ||
| import { ActionCreator } from 'typescript-fsa'; | ||
|
|
||
| import { esFilters, esQuery } from '../../../../../../../../../src/plugins/data/common/es_query'; |
| import { WorkspaceField, AdvancedSettings } from './app_state'; | ||
|
|
||
| // eslint-disable-next-line @typescript-eslint/no-empty-interface | ||
| interface JsonArray extends Array<JsonValue> {} |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
flash1293
left a comment
There was a problem hiding this comment.
Graph changes LGTM, thanks for the improvement 👍
* Explicit namespaces for esQuery and esQuery * Remove unnecessary file from siem * remove jsonvalue definition from siem * server FieldFormatsRegistry, Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
* Explicit namespaces for esQuery and esQuery * Remove unnecessary file from siem * remove jsonvalue definition from siem * server FieldFormatsRegistry, Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
Part of #56881
This PR applies the proposed resolution for #52374, trying to balance code readability, API discoverability, DX and documentation generation using ApiExtractor on the
esQueryandesKuerynamespaces ofdataplugin.The solution involves:
Checklist
Delete any items that are not applicable to this PR.
For maintainers