Open
Conversation
Signed-off-by: Tierney Cyren <hello@bnb.im>
Signed-off-by: Tierney Cyren <hello@bnb.im>
Author
|
I'll work on a docs PR now ✅ |
6 tasks
This file contains hidden or 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
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.
🔗 Linked issue
#172
❓ Type of change
📚 Description
This PR adds
pushToTopandpushToTopOnceand adds tests forpushToTop, mirroringpushTo's tests. I've run the tests locally and it works.I've got a situation where I have a list of events in the future and in the past, and I want the ones in the past to be in reverse chronological order but the ones in the future to be in chronological order. Rather than having to do that logic in JS, it'd be super nice to just be able to do that with Edge.
pushToTopmakes it super simple to set the events in the past in reverse chronological order without any JS logic around this in my app.📝 Checklist