-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: dryRedo on replay_bloc #3551
Comments
Hello, |
I love bloc and cubit, but I'm fighting with a few limitations.
Imagine Cubit as the Navigation stack (back/forward button, etc).
I wish I could do this:
trash.contains(dryRedo())
. I don't want to redo. I want to know if I can redo based on redo value without removing it from its stack.Possible Desired Solutions
history.range(index, history.length)
and get the forward redo history.List<T> undoValues(int? limit)
andList<T> redoValues(int? limit)
, soredoValues(1).first
would do what I want.The last one is slightly more verbose but seems better. I also like the second one. If it were public inside the bloc, at least, I would be able to fix myself. Maybe with tuples it could be
(int, ?) getHistoryIndex
.The text was updated successfully, but these errors were encountered: