Bug when importing PDF to Obsidian.

[DudeThatsErin]

I would expect to see a copy of the PDF saved to Obsidian and not the information from the PDF copied to Obsidian. It looks ridiculous lol

This screenshot shows exactly what I am seeing on my iPad.

[jacksonh]

Thanks, it looks like it grabbed our search content, not the actual PDF document here. Does this happen with all PDFs or happened with just this one?

[sywhb]

Hey @DudeThatsErin , there is another variable in the template: fileAttachment which could be used to export PDF as an attachment in Obsidian.

I can create an attachment using below template.

![[{{{fileAttachment}}}]]

[sywhb]

@jacksonh I guess I should set content to null if the type of the item is FILE so we won't pull the search content from the PDF

[jacksonh]

@sywhb there is a contentReader attribute that should be set to WEB for any web article. That is probably the best way to do it.

[sywhb]

@jacksonh sorry, I mean in Obsidian template

[jacksonh]

Yeah i think when generating the template values you can do something like:

content" article.contentReader === 'WEB' ? article.content : null

[sywhb]

Yeah!

[andresrinivasan]

I expected

{{#fileAttachment}}
![[{{{fileAttachment}}}]]
{{/fileAttachment}}

{{^fileAttachment}}
{{{content}}}
{{/fileAttachment}}

to accomplish the above.

{#fileAttachment}... works as expected and only renders fileAttachment for FILE content.

{^fileAttachment}... does not render the content when fileAttachment is false.

[sywhb]

I have created a PR #137 so that we will return content as undefined if we are syncing a PDF @jacksonh

[github-actions[bot]]

:tada: This issue has been resolved in version 1.6.3 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: