Skip to content

feat: add animations to popper#1594

Merged
shinokada merged 1 commit intothemesberg:mainfrom
jjagielka:popper-animations
May 15, 2025
Merged

feat: add animations to popper#1594
shinokada merged 1 commit intothemesberg:mainfrom
jjagielka:popper-animations

Conversation

@jjagielka
Copy link
Copy Markdown
Contributor

@jjagielka jjagielka commented May 15, 2025

📑 Description

Add possibility to use transitions on all Popper descendants.

Status

  • Not Completed
  • Completed

✅ Checks

  • My pull request adheres to the code style of this project
  • My code requires changes to the documentation
  • I have updated the documentation as required
  • I have checked the page with https://validator.unl.edu/
  • All the tests have passed
  • My pull request is based on the latest commit (not the npm version).

ℹ Additional Information

Summary by CodeRabbit

  • New Features
    • Added support for customizable transitions and transition parameters to popover and tooltip components, allowing for animated show/hide effects.
  • Documentation
    • Updated tooltip documentation with a new section on configuring animations, including examples of using different Svelte transitions.

@vercel
Copy link
Copy Markdown

vercel bot commented May 15, 2025

@jjagielka is attempting to deploy a commit to the Themesberg Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented May 15, 2025

Walkthrough

The Popper.svelte component was refactored to use Svelte's transition system for popover animations, introducing customizable transition props and shifting visibility control from imperative DOM methods to reactive state and Svelte lifecycle events. Documentation for tooltips was updated to include a new section on configuring tooltip animations using Svelte transitions.

Changes

File(s) Change Summary
src/lib/utils/Popper.svelte Refactored to use Svelte transitions for popover visibility; added transition and transitionParams props; updated control flow to use reactive state and Svelte lifecycle events; improved separation of concerns.
src/routes/docs/components/tooltip.md Added an "Animations" section with examples showing how to use Svelte transitions for tooltip animations; no API changes.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant TriggerElement
    participant PopperComponent
    participant SvelteTransition

    User->>TriggerElement: Interact (e.g., hover, click)
    TriggerElement->>PopperComponent: Event triggers isOpen = true
    PopperComponent->>SvelteTransition: Start transition (e.g., fade, slide)
    SvelteTransition-->>PopperComponent: onintrostart event
    PopperComponent->>PopperComponent: showPopover()
    User->>TriggerElement: Stop interaction
    TriggerElement->>PopperComponent: Event triggers isOpen = false
    PopperComponent->>SvelteTransition: Start outro transition
    SvelteTransition-->>PopperComponent: onoutroend event
    PopperComponent->>PopperComponent: hidePopover()
Loading

Poem

In the meadow of code, transitions now bloom,
Popovers and tooltips with animated room.
From fade to slide, they elegantly show,
With Svelte’s magic touch, they gracefully go.
A hop, a jump, a whisker’s delight—
Rabbits and tooltips both take flight!
🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
src/lib/utils/Popper.svelte (1)

27-29: Consider improving transition parameter defaults.

The default transition duration of 100ms might be too quick for smooth animations in some cases.

-const paramsDefault = { duration: 100, easing: sineIn };
+const paramsDefault = { duration: 150, easing: sineIn };
src/routes/docs/components/tooltip.md (1)

151-163: Comprehensive examples of different transition types.

The examples demonstrate a good variety of transition types (blur, slide, scale) and show how to customize transition parameters, which is very helpful for users.

Consider adding a brief explanation of common transition parameters like duration, delay, and easing to make it more beginner-friendly.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 9899964 and d6cf3f3.

📒 Files selected for processing (2)
  • src/lib/utils/Popper.svelte (4 hunks)
  • src/routes/docs/components/tooltip.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Playwright and Lint
🔇 Additional comments (7)
src/lib/utils/Popper.svelte (6)

5-7: Good addition of Svelte transition imports.

The imports for Svelte transitions and easing functions are appropriate for implementing the animation functionality.


11-11: Good implementation of transition props with sensible defaults.

The addition of transition and transitionParams props with appropriate defaults (fade transition with no custom parameters) allows for customizable animations while maintaining backward compatibility.


17-17: Appropriate conversion to reactive state.

Converting popover and arrowParams to reactive state variables is a good practice that aligns with Svelte's reactivity system and makes the state management more consistent.

Also applies to: 21-25


66-74: Simplified state management in open_popover.

Good refactoring by removing direct DOM manipulation and using reactive state management instead. This approach is more aligned with Svelte's declarative patterns.


109-117: Improved toggle handling with centralized state updates.

The refactored toggle handler now centralizes the state management, making the code more maintainable and easier to understand.


166-175: Great implementation of conditional rendering with transitions.

The conditional rendering approach with Svelte transitions is a significant improvement over the previous implementation:

  1. It follows Svelte's paradigm of declarative UI
  2. It properly integrates with the component lifecycle
  3. It enables customizable animations
  4. It correctly synchronizes with the popover API using lifecycle events

The onintrostart and onoutroend events are used appropriately to call the native popover methods.

src/routes/docs/components/tooltip.md (1)

146-149: Good addition of animations documentation section.

The new section on animations is a valuable addition to help users understand how to apply transitions to tooltips.

@shinokada
Copy link
Copy Markdown
Collaborator

shinokada commented May 15, 2025

This should fix no.3 of #1588 as well.

@jjagielka
Copy link
Copy Markdown
Contributor Author

That was the purpose.

@shinokada
Copy link
Copy Markdown
Collaborator

I will add animation examples to popover.
Thanks.

@shinokada shinokada merged commit d6cf3f3 into themesberg:main May 15, 2025
1 of 2 checks passed
@jjagielka jjagielka deleted the popper-animations branch May 15, 2025 09:27
@coderabbitai coderabbitai bot mentioned this pull request Oct 15, 2025
8 tasks
@coderabbitai coderabbitai bot mentioned this pull request Nov 1, 2025
8 tasks
This was referenced Jan 11, 2026
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