-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explicit namespaces for esFilters #57177
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kibana app changes LGTM
@@ -58,7 +57,7 @@ export const buildQueryBarDescription = ({ | |||
<EuiFlexItem grow={false} key={`${field}-filter-${index}`}> | |||
<EuiBadgeWrap color="hollow"> | |||
{indexPatterns != null ? ( | |||
<FilterLabel | |||
<esFilters.FilterLabel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I appreciate that!!!! That's great
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maps changes LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should these be put under a namespace of some sort?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will get there! :)
@@ -20,8 +20,36 @@ | |||
import { PluginInitializerContext } from '../../../core/server'; | |||
import { DataServerPlugin, DataPluginSetup, DataPluginStart } from './plugin'; | |||
|
|||
import { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I understand why these SIEM files were deleted... could you explain?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They duplicated files from our repo, requiring some really internal types that shouldn't be exported.
I instead exported FilterLabel
and used that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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