-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Date nanos context typescript conversion #38735
Date nanos context typescript conversion #38735
Conversation
- too much shared code
- merge fetchPredecessorRows & fetchSuccessorRows - new function fetchSurroundingRows - less code duplication
This comment has been minimized.
This comment has been minimized.
💚 Build Succeeded |
Pinging @elastic/kibana-app |
…_nanos-context-typescript
💚 Build Succeeded |
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, tested and everything still seems to work correctly. Added two comments about position of the files, but that's nothing important
I've got no idea, why suddenly there's a request by Kibana-Design necessary?? |
@kertal Because you changed https://github.com/elastic/kibana/pull/38735/files#diff-6a10bcd18378ed330fcf2b897d13493eL138 - every change in scss files triggers this review |
25f47a3
to
8971b9c
Compare
@flash1293 thx, already found and fixed it, commit didn't belong here |
💚 Build Succeeded |
Summary
Convert parts of the discover context view to TypeScript, Follow up of #38023
Checklist
Use
strikethroughsto remove checklist items you don't feel are applicable to this PR.- [ ] This was checked for cross-browser compatibility, including a check against IE11- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support- [ ] Documentation was added for features that require explanation or tutorials- [ ] Unit or functional tests were updated or added to match the most common scenarios- [ ] This was checked for keyboard-only and screenreader accessibilityFor maintainers
- [ ] This was checked for breaking API changes and was labeled appropriately- [ ] This includes a feature addition or change that requires a release note and was labeled appropriately