leptos-animated-for

KO | EN

gitlite — search

#javascript #python #typescript #golang #android #machine-learning #rust #linux #docker #windows #cli #kubernetes #vue #security

leptos-animated-for

(★ 36)

💫 List-rendering component utilizing FLIP position transitions for Leptos

leptos-animated-for Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

## ⚠️ This crate is no longer maintained ⚠️

I've created [leptos-animate](https://github.com/brofrain/leptos-animate) as a successor to this crate with a more flexible API and more features.\
Consider using it instead.

# `<AnimatedFor />` component for [Leptos](https://leptos.dev/)

[FLIP](https://aerotwist.com/blog/flip-your-animations/) animations for element and component groups inspired by Vue's [`<TransitionGroup>`](https://vuejs.org/guide/built-ins/transition-group.html).

This crate exports a component similar to Leptos' built-in [`<For />`](https://docs.rs/leptos/latest/leptos/fn.For.html) with additional properties for applying specific CSS classes to nodes that:

- are rendered for the first time

- represent already removed items

- have their positions changed due to reorder or other elements being added / removed

Each node has to be uniquely keyed, since the original `<For />`'s logic is used under the hood. Additionally, animations will break for unstable or duplicate keys. You can refer to the official [`<For />` guide](https://leptos-rs.github.io/leptos/view/04_iteration.html#dynamic-rendering-with-the-for-component) for more detailed information.

## Usage

```rs
view! {
    <AnimatedFor
        each=items
        key=|item| item.unique_key
        children=|item| view! { /* ... */ }
        enter_from_class="before-enter-animation"
        enter_class="enter-animation"
        move_class="move-animation"
        leave_class="leave-animation"
        appear=true
    />
}
```

- `enter_from_class` - class applied to each new element for a single tick. Then the class is removed and `enter_class` is inserted instead. This is useful for defining the initial state of an element (e.g. full transparency) before the enter animation starts.

- `enter_class` - appended to entering elements. The class is removed on a [transitionend](https://developer.mozilla.org/en-US/docs/Web/API/Element/transitionend_event) or [animationend](https://developer.mozilla.org/en-US/docs/Web/API/Element/animationend_event) event, or if move transition is triggered before this one ends.

- `move_class` - active class for elements moving to their new positions. The class is removed on a `transitionend` or `animationend` event (same as `enter_class`). Reordering items again before they reach their destinations will overwrite the target positions.

- `leave_class` - removed items have their "zombie" elements present in the DOM with this class applied. The nodes are finally deleted on a `transitionend` or `animationend` event.

- `appear` - if true, the enter transition triggers for all children on initial `<AnimatedFor />` render.

Example usage with [TailwindCSS](https://tailwindcss.com/):

```rs
view! {
     <AnimatedFor
        each=items
        key=|item| item.id
        children=|item| item.view
        enter_from_class="opacity-0"
        enter_class="duration-800"
        move_class="duration-1200"
        leave_class="opacity-0 duration-500"
        appear=true
    />
}
```

Check out `examples` directory for a complete code.

### SSR support

It generally should just work. See this [example](https://github.com/brofrain/leptos-animated-for/blob/main/examples/ssr).

## Known issues

- Given a child element with always present `transition` or `transition-duration` style property, move transition breaks if triggered before the previous move transition has finished.\
  Unless the children are reordered frequently, this should not be a problem.\
  To prevent the glitch from occurring, make sure that the transition-related properties are applied only via `enter_class`, `move_class`, or `leave_class` props. In case you need the transitions for e.g. hover animations, you can wrap the elements in additional `<div>` nodes, so `<AnimatedFor />` can work on them instead.\
  As of writing this, I'm not sure how to fix this, but I will investigate this in the future.

- Elements rendered on server-side have no `enter_from_class` applied initially. In combination with `appear` prop, the nodes may be visible for a short time before the enter animation starts.\
  If you care about the initial entering transition, make sure that the list is rendered only in the browser.

## TODO

- [ ] Tests
- [ ] Investigate the known issues
- [ ] Detect duplicate keys for better developer experience
- [ ] Add ability to define custom handlers when an element enters "before enter" / "enter" / "move" / "leave" state
- [ ] Optional properties for explicit animation durations
- [ ] Optional bool prop for enabling resize animations
- [ ] Optional bool prop for assigning a static `z-index` to each child, so triggering a move transition before the previous one has finished doesn't cause overlapping elements to be chaotically moved from front to back and vice versa.

## License

[MIT License](https://opensource.org/licenses/MIT)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

leptos-animated-for

leptos-animated-for Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

leptos-animated-for

leptos-animated-for Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README