-
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
[Fleet[ Allow to specify a datastream id in the edit integration page #135321
[Fleet[ Allow to specify a datastream id in the edit integration page #135321
Conversation
Pinging @elastic/fleet (Team:Fleet) |
packagePolicyId, | ||
}); | ||
|
||
return `${baseUrl}${dataStreamId ? `?datastreamId=${encodeURIComponent(dataStreamId)}` : ''}`; |
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.
it would be nice to add some unit tests on the url building logic
@@ -43,13 +44,13 @@ const ShortenedHorizontalRule = styled(EuiHorizontalRule)` | |||
const shouldShowStreamsByDefault = ( |
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.
it would be great to test this logic, maybe you could move this to a helper function so it can be tested without the component
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.
LGTM
@elasticmachine merge upstream |
💛 Build succeeded, but was flakyFailed CI StepsTest Failures
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @nchaulet |
Summary
Related to #133740
Allow to specify a
datastreamId
in the package policy editor UI to navigate back to the datastream when viewing custom pipeline or mappings.UI Changes
demo-nav.mov