Thanks to visit codestin.com
Credit goes to github.com

Skip to content

feat: pass speed options#682

Merged
olzhik11 merged 1 commit intodevfrom
hotfix/player-speed
Jul 4, 2025
Merged

feat: pass speed options#682
olzhik11 merged 1 commit intodevfrom
hotfix/player-speed

Conversation

@olzhik11
Copy link
Member

@olzhik11 olzhik11 commented Jul 4, 2025

  • override default speed options
    Screenshot 2025-07-04 at 1 00 44 PM

Important

Adds configurable speed options to session player components in session-player.tsx and shared/session-player.tsx.

  • Behavior:
    • Adds speedOptions constant to define available speed settings in session-player.tsx and shared/session-player.tsx.
    • Passes speedOptions to rrwebPlayer configuration in session-player.tsx and shared/session-player.tsx.
    • Updates speed dropdown to use speedOptions in session-player.tsx and shared/session-player.tsx.
  • Misc:
    • Minor UI adjustments in session-player.tsx and shared/session-player.tsx to accommodate speed options.

This description was created by Ellipsis for b8a30f7. You can customize this summary. It will automatically update as commits are pushed.

@olzhik11 olzhik11 requested a review from skull8888888 July 4, 2025 12:01
@olzhik11 olzhik11 self-assigned this Jul 4, 2025
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed everything up to b8a30f7 in 1 minute and 55 seconds. Click for details.
  • Reviewed 59 lines of code in 2 files
  • Skipped 0 files when reviewing.
  • Skipped posting 6 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. frontend/components/shared/traces/session-player.tsx:36
  • Draft comment:
    Consider extracting the speedOptions constant to a shared module to avoid duplication across components.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% The speedOptions array is only used within this component. There's no evidence provided that this array is duplicated elsewhere or needs to be shared. The comment is speculative about potential future duplication. Moving it to a shared module would add complexity without clear benefit. I could be wrong if there are other components that use the same speed options array, but I don't have access to see that. The comment might be based on knowledge of the broader codebase. Without evidence of actual duplication, suggesting to extract this simple array to a shared module is premature optimization and could add unnecessary complexity. Delete the comment. While the suggestion might be valid if there's duplication elsewhere, we don't have evidence of that, and the current usage is appropriately scoped to this component.
2. frontend/components/shared/traces/session-player.tsx:149
  • Draft comment:
    Verify that the prop key 'speedOption' is correct per rrwebPlayer API; the singular key with plural constant may be confusing.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 30% <= threshold 50% The comment is asking the author to verify the correctness of a prop key, which is against the rules. However, it does point out a potential issue with the naming convention, which could be useful. The comment could be rephrased to suggest a change or ask for confirmation of intention, but as it stands, it violates the rules.
3. frontend/components/shared/traces/session-player.tsx:312
  • Draft comment:
    Refactoring the dropdown mapping to use the speedOptions constant improves maintainability.
  • Reason this comment was not posted:
    Comment was not on a location in the diff, so it can't be submitted as a review comment.
4. frontend/components/traces/session-player.tsx:42
  • Draft comment:
    Duplicate speedOptions constant detected; consider centralizing shared constants if used in multiple files.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% The comment appears to be incorrect. The speedOptions array is only defined once in this file and is reused in two places within the same file - this is good practice for DRY code. There's no evidence of duplication. The comment suggests centralizing it if used in multiple files, but we don't have evidence it's used elsewhere. I could be missing other files in the codebase where this constant might be duplicated. The comment might be based on knowledge of duplicates elsewhere. Even if the constant exists elsewhere, we can only evaluate what we see in this file. The comment makes an assumption about code we can't verify, violating our rule about needing strong evidence. Delete this comment. The constant is not duplicated within this file, and we cannot verify claims about duplication across files.
5. frontend/components/traces/session-player.tsx:243
  • Draft comment:
    Ensure the 'speedOption' prop passed inside rrwebPlayer's config is correct; consider renaming to 'speedOptions' if that aligns with the API.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% The comment points out what could be a real API mismatch - using speedOption vs speedOptions. However, without seeing the rrwebPlayer library's actual API documentation, I can't be 100% certain which prop name is correct. The fact that the code is using speedOption suggests that might be the correct name, since it's presumably working. The comment is speculative without strong evidence. I don't have access to the rrwebPlayer library's documentation to verify the correct prop name. The code might actually be working fine as-is. Without being able to verify the correct prop name in the library's API, this comment is too speculative. We should assume the author tested this and it's working. Delete the comment since we don't have strong evidence that it's incorrect, and the code is likely working as-is.
6. frontend/components/traces/session-player.tsx:416
  • Draft comment:
    Using the speedOptions constant for rendering dropdown items enhances consistency and maintainability.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative and does not provide any actionable feedback or suggestions for improvement. It simply states a benefit of using a constant, which is not necessary for the PR author to know.

Workflow ID: wflow_3pfIF24ZvkhS3FpK

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@olzhik11 olzhik11 merged commit a27b89e into dev Jul 4, 2025
3 checks passed
@olzhik11 olzhik11 deleted the hotfix/player-speed branch July 4, 2025 15:32
dinmukhamedm added a commit that referenced this pull request Jul 8, 2025
…script (#690)

* feat: pass speed options (#682)

* remove cloning attributes as much as possible (#681)

* wip: remove cloning attributes as much as possible

* small refactor for testability + clone after filter

* tiny change, remove unnecessary ref

* add unit testing

* feat: enhance traces/shared traces (#683)

* feat: enhance traces WIP

* feat: update shared trace

* feat: refactor styles, add space listener, fix hydration error

* feat: trace id fix, default props to store, refactor store

* feat: add spanId as prop, fix navigation config

* feat: remove logs, add orderby to spans search

* feat: fix comments

* feat: update table columns

* feat: fix default width on client side

* feat: update evaluation trace view

* remove clones, slight refactor, .remove from hashmap where possible (#684)

* remove clones, slight refactor, .remove from hashmap where possible

* replace ai.prompt.tools in place per ellipsis

* Feat/custom renderer (#676)

* feat: custom renderer wip

* feat: custom renderer

* feat: update to jsx renderer

* fix

* feat: small fixes

* remove hover

* feat: refactor

* feat: fix update of custom renderer

* feat: update custom renderer

* fixes

---------

Co-authored-by: Robert Kim <[email protected]>

* feat: add telemetry (#686)

* feat: add telemetry

* feat: run otel only in prod

* allocator (#687)

* cleanup unused DB schema and code (#685)

* cleanup unused DB schema and code

* fix build

* return newly created tag class

* address ellipsis

* feat: fix css in rrweb events (#688)

* Feat/lam 653 (#678)

* feat: add domain check logic

* feat: remove agent chat feature

* feat: remove idnex from landing, .env

* feat: remove hardcoded value

* fix: link

* feat: revert

* update @codemirror/language (#691)

* fix: update cache update query to new pricing mode (#689)

* force update lockfile

---------

Co-authored-by: Olzhas Nurpeisov <[email protected]>
Co-authored-by: Robert Kim <[email protected]>
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