-
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
[Logs UI] Use react-intl FormattedRelative instead of a custom component #33146
Merged
weltenwort
merged 1 commit into
elastic:master
from
weltenwort:logs-ui-fix-relative-time-state-update
Mar 18, 2019
Merged
[Logs UI] Use react-intl FormattedRelative instead of a custom component #33146
weltenwort
merged 1 commit into
elastic:master
from
weltenwort:logs-ui-fix-relative-time-state-update
Mar 18, 2019
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
weltenwort
added
v8.0.0
Feature:Logs UI
Logs UI feature
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
v7.2.0
labels
Mar 13, 2019
Pinging @elastic/infrastructure-ui |
💚 Build Succeeded |
weltenwort
changed the title
Use react-intl relative time component instead
[Logs UI] Use react-intl FormattedRelative instead of a custom component
Mar 13, 2019
Kerry350
approved these changes
Mar 18, 2019
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.
this should eliminate the state update race condition you noticed
Nice 👍
LGTM!
weltenwort
added a commit
to weltenwort/kibana
that referenced
this pull request
Mar 18, 2019
…ent (elastic#33146) This replaces the custom relative time component in the Logs UI live streaming inline loading indicator with the one from `react-intl`. This was not done at the time of the initial i18n introduction (elastic#25213), because of elastic#26237, which apparently has since been resolved via elastic#26468. Visual changes should be limited to `now` being shown instead of `0s ago`.
weltenwort
added
the
non-issue
Indicates to automation that a pull request should not appear in the release notes
label
May 23, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature:Logs UI
Logs UI feature
non-issue
Indicates to automation that a pull request should not appear in the release notes
review
Team:Infra Monitoring UI - DEPRECATED
DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
v7.2.0
v8.0.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This replaces the custom relative time component in the Logs UI live streaming inline loading indicator with the one from
react-intl
. This was not done at the time of the initial i18n introduction (#25213), because of #26237, which apparently has since been resolved via #26468. Visual changes should be limited tonow
being shown instead of0s ago
.Checklist
Documentation was added for features that require explanation or tutorialsUnit or functional tests were updated or added to match the most common scenariosThis was checked for keyboard-only and screenreader accessibilityFor maintainers
This was checked for breaking API changes and was labeled appropriatelyThis includes a feature addition or change that requires a release note and was labeled appropriately