Explicit namespaces for esFilters#57177
Conversation
…izozom/kibana into newplatform/data/kuery-query-namespace
…filters-namespace-O_O
…filters-namespace-O_O
…ata/filters-namespace-O_O
|
Pinging @elastic/kibana-app-arch (Team:AppArch) |
|
@elasticmachine merge upstream |
flash1293
left a comment
There was a problem hiding this comment.
Kibana app changes LGTM
| <EuiBadgeWrap color="hollow"> | ||
| {indexPatterns != null ? ( | ||
| <FilterLabel | ||
| <esFilters.FilterLabel |
There was a problem hiding this comment.
I appreciate that!!!! That's great
lukasolson
left a comment
There was a problem hiding this comment.
Left a few minor comments below. Overall, LGTM. Pulled down and tested in Chrome and things looked good.
|
|
||
| export function getFilter( | ||
| store: esFilters.FilterStateStore, | ||
| store: any, // I don't want to export only for this, as it should move to data plugin |
There was a problem hiding this comment.
Do you want to make a follow-up PR or issue for this so we don't forget?
There was a problem hiding this comment.
Specifically, this piece of code should actually go away as soon as state management migration is done.
But I created an issue for other follow ups needed.
| createSavedQueryService, | ||
| syncAppFilters, | ||
| syncQuery, | ||
| getTime, | ||
| getQueryLog, | ||
| getQueryStateContainer, |
There was a problem hiding this comment.
Should these be put under a namespace of some sort?
| import { PluginInitializerContext } from '../../../core/server'; | ||
| import { DataServerPlugin, DataPluginSetup, DataPluginStart } from './plugin'; | ||
|
|
||
| import { |
There was a problem hiding this comment.
Do we need to export a separate namespace for both public/server or can we create the namespace inside the common folder and just re-export here and in public?
There was a problem hiding this comment.
We do need separate namespaces for public \ server as they have really different needs @lukeelmers
| @@ -1,95 +0,0 @@ | |||
| /* | |||
There was a problem hiding this comment.
I'm not sure I understand why these SIEM files were deleted... could you explain?
There was a problem hiding this comment.
They duplicated files from our repo, requiring some really internal types that shouldn't be exported.
I instead exported FilterLabel and used that.
poffdeluxe
left a comment
There was a problem hiding this comment.
Canvas changes look good
…ata/filters-namespace-O_O
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
|
Forcing merge because I copied the fix from #57421 and now it requires an additional review from ML. |
* Explicit namespaces for esQuery and esQuery * Remove unnecessary file from siem * remove jsonvalue definition from siem * esFilters refactor O_O * Delete IFilterType * import fixes * Fix merge 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 * esFilters refactor O_O * Delete IFilterType * import fixes * Fix merge Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
FrankHassanabad
left a comment
There was a problem hiding this comment.
Looked at the server side and it is LGTM for us
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 filters helper namespace
Checklist
Delete any items that are not applicable to this PR.
For maintainers