Skip to content
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

Time Travel timestamps as strings, durations as numbers #59

Merged
merged 1 commit into from
Nov 10, 2017

Conversation

fbarl
Copy link
Contributor

@fbarl fbarl commented Nov 3, 2017

Fixes #58.

Keeping timestamp arguments as plain strings removes the client app's dependency on moment.js and more importantly, enables React to do shallow comparison of props and be smarter about whether they've changed.

To make sure it works well in context of Weave Cloud, it might be best to test by proxying service-ui with both scope and ui-components repos, e.g.

PROXY_SCOPE_COMPONENT=true SCOPE_PATH=/home/fbarl/Projects/weaveworks/scope/ PROXY_COMPONENTS=true COMPONENT_LIB_PATH=/home/fbarl/Projects/weaveworks/ui-components/ SERVICE_HOST=frontend.dev.weave.works yarn start

@fbarl fbarl self-assigned this Nov 3, 2017
@fbarl
Copy link
Contributor Author

fbarl commented Nov 3, 2017

@fbarl fbarl force-pushed the 58-make-time-travel-timestamp-params-strings branch from 8eb509c to 7c5f922 Compare November 9, 2017 16:14
@fbarl fbarl force-pushed the 58-make-time-travel-timestamp-params-strings branch from 7c5f922 to 478d84b Compare November 9, 2017 16:23
@fbarl fbarl requested a review from jpellizzari November 9, 2017 16:27
@fbarl fbarl changed the title [WIP] Time Travel timestamps as strings, durations as numbers Time Travel timestamps as strings, durations as numbers Nov 9, 2017
@fbarl fbarl merged commit 8c6daf2 into master Nov 10, 2017
@fbarl fbarl deleted the 58-make-time-travel-timestamp-params-strings branch November 24, 2017 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants