Skip to content

Desktop: Importing from OneNote: Convert an ink-related import error to a warning#15197

Open
personalizedrefrigerator wants to merge 2 commits intolaurent22:devfrom
personalizedrefrigerator:pr/desktop/onenote-import/allow-ink-to-have-no-strokes
Open

Desktop: Importing from OneNote: Convert an ink-related import error to a warning#15197
personalizedrefrigerator wants to merge 2 commits intolaurent22:devfrom
personalizedrefrigerator:pr/desktop/onenote-import/allow-ink-to-have-no-strokes

Conversation

@personalizedrefrigerator
Copy link
Copy Markdown
Collaborator

Problem

A user has reported that it's possible to trigger the ink data node has no strokes error on the Joplin forum. Either:

  1. There's a bug in the parser or ID resolution logic that prevents Joplin from finding the ink data node, or
  2. It's possible for an ink data node to have no associated InkStrokes object.

(At the time of this writing, no test .one file 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 InkStrokes objects.

@coderabbitai coderabbitai Bot added bug It's a bug desktop All desktop platforms import Related to importing files such as ENEX, JEX, etc. labels Apr 25, 2026
@github-actions github-actions Bot deleted a comment from coderabbitai Bot Apr 25, 2026
@personalizedrefrigerator personalizedrefrigerator changed the title Desktop: Importing from OneNote: Convert an ink-related import error from an error to a warning Desktop: Importing from OneNote: Convert an ink-related import error to a warning Apr 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug It's a bug desktop All desktop platforms import Related to importing files such as ENEX, JEX, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant