Desktop: Importing from OneNote: Convert an ink-related import error to a warning#15197
Open
personalizedrefrigerator wants to merge 2 commits intolaurent22:devfrom
Conversation
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.
Problem
A user has reported that it's possible to trigger the
ink data node has no strokeserror on the Joplin forum. Either:InkStrokesobject.(At the time of this writing, no test
.onefile has been provided).Solution
Convert the error to a warning: This pull request assumes that this isn't caused by a bug in the parser and that OneNote can create ink data nodes with no
InkStrokesobjects.