feat: add animation possibility to asyncbinding #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kristofkalai
force-pushed
the
feat/add-animation-possibility
branch
from
458cf1c
to
0e1c5fa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As described in issue #2,
AsyncBindingcurrently lacks support for animation. This pull request addresses this limitation by introducing animation capabilities. Additionally, two examples have been provided to better illustrate the problem. These examples can be accessed here: the latest two commits include a basic view and a list where animations could be implemented, and can enhance the user experience.Backward compatibilty
Thanks to the default arguments, the library remains fully backward compatible. By default it uses
nilaz an animation, which means no animation (as it was before this pull request).