fix(ui): error calling set-step! in bug-report#8328
Merged
Conversation
situ2001
reviewed
Jan 12, 2023
Comment on lines
-47
to
-48
| reset-step! (fn [] ((set-step! 0) | ||
| (set-result! {})))] |
Contributor
There was a problem hiding this comment.
Haven't noticed that there is an extra (), sorry.
Collaborator
Author
There was a problem hiding this comment.
Never mind. I noticed some error logs while clicking around buttons.
situ2001
reviewed
Jan 12, 2023
Comment on lines
+47
to
+48
| reset-step! (fn [] | ||
| (set-step! 0) |
cnrpman
pushed a commit
to cnrpman/logseq
that referenced
this pull request
Jan 12, 2023
sallto
pushed a commit
to sallto/logseq
that referenced
this pull request
Jan 18, 2023
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
3 participants
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.
Introduced in #8317
CC @situ2001