-
Notifications
You must be signed in to change notification settings - Fork 405
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
TimeLine animation range #3291
TimeLine animation range #3291
Conversation
web/client/epics/playback.js
Outdated
module.exports = { | ||
retrieveFramesForPlayback: (action$, { getState = () => { } } = {}) => | ||
action$.ofType(PLAY).exhaustMap( () => | ||
getDomainValues(...domainArgs(getState)) | ||
getDomainValues(...domainArgs(getState, { | ||
time: domainRangeIdentify(playbackRangeSelector(getState()).startPlaybackTime, playbackRangeSelector(getState()).endPlaybackTime) |
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 this transformation inside domainArgs
, it is needed also at line 58 (next windows of values requests)
web/client/epics/playback.js
Outdated
@@ -39,10 +39,14 @@ const domainArgs = (getState, paginationOptions = {}) => { | |||
...paginationOptions | |||
}]; | |||
}; | |||
const domainRangeIdentify = (start, end) => `${start}/${end}`; |
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.
As I said in another comment, you have to move this transformation inside domainArgs
function.
Anyway if you want to keep a function to identify this operation, you must find a better name.
Checking this probably a good name is something like toAbsoluteInterval
Description
Issues
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
What is the current behavior? (You can also link to an open issue here)
see the description
What is the new behavior?
see the description
Does this PR introduce a breaking change? (check one with "x", remove the other)
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: