[GH-ISSUE #5193] [Bug] Exporting link previews should export to []() format #2301

Closed
opened 2026-03-23 21:21:15 +00:00 by mirror · 6 comments
Owner

Originally created by @Xazin on GitHub (Apr 23, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5193

Originally assigned to: @Xazin, @Omegaviv on GitHub.

Bug Description

When exporting a document to markdown that contains link previews, they should be exported to the Markdown format [Page title](https://link.com/image.png). (We store the url and title metadata, use this to build the markdown link)

Original author: https://discord.com/channels/903549834160635914/903553722804748309/1232305891643232317

How to Reproduce

Export a document containing link previews to Markdown

Expected Behavior

The links are transformed to proper markdown format

Operating System

All

AppFlowy Version(s)

0.5.4

Screenshots

No response

Additional Context

No response

Originally created by @Xazin on GitHub (Apr 23, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5193 Originally assigned to: @Xazin, @Omegaviv on GitHub. ### Bug Description When exporting a document to markdown that contains link previews, they should be exported to the Markdown format `[Page title](https://link.com/image.png)`. _(We store the url and title metadata, use this to build the markdown link)_ Original author: https://discord.com/channels/903549834160635914/903553722804748309/1232305891643232317 ### How to Reproduce Export a document containing link previews to Markdown ### Expected Behavior The links are transformed to proper markdown format ### Operating System All ### AppFlowy Version(s) 0.5.4 ### Screenshots _No response_ ### Additional Context _No response_
mirror 2026-03-23 21:21:15 +00:00
Author
Owner

@Omegaviv commented on GitHub (May 9, 2024):

@Xazin can I work on this?

<!-- gh-comment-id:2101914828 --> @Omegaviv commented on GitHub (May 9, 2024): @Xazin can I work on this?
Author
Owner

@Omegaviv commented on GitHub (May 10, 2024):

@LucasXu0 as @Xazin has mentioned to display Page title and url, so according to the current implementation there is no Page title metadata on LinkPreviewNode

image
<!-- gh-comment-id:2104778679 --> @Omegaviv commented on GitHub (May 10, 2024): @LucasXu0 as @Xazin has mentioned to display Page title and url, so according to the current implementation there is no Page title metadata on LinkPreviewNode <img width="393" alt="image" src="https://github.com/AppFlowy-IO/AppFlowy/assets/86337946/8fc10374-ea3f-4bbe-bbb6-f5c5d2895e69">
Author
Owner

@Xazin commented on GitHub (May 10, 2024):

@LucasXu0 as @Xazin has mentioned to display Page title and url, so according to the current implementation there is no Page title metadata on LinkPreviewNode

This requires a change to the Link Preview Block, we should store the metadata when it's first loaded on the node itself.

What if the site has changed since? We can add an action to reload the metadata in case the author thinks it's wrong, which would go on to refetch the metadata. This way we also don't have to refetch it for every single user, it's enough to fetch it once for all users.

<!-- gh-comment-id:2104798785 --> @Xazin commented on GitHub (May 10, 2024): > @LucasXu0 as @Xazin has mentioned to display Page title and url, so according to the current implementation there is no Page title metadata on LinkPreviewNode > This requires a change to the Link Preview Block, we should store the metadata when it's first loaded on the node itself. What if the site has changed since? We can add an action to reload the metadata in case the author thinks it's wrong, which would go on to refetch the metadata. This way we also don't have to refetch it for every single user, it's enough to fetch it once for all users.
Author
Owner

@Omegaviv commented on GitHub (May 13, 2024):

okay I will create a issue on AppFlowy-plugin repository and push the changes there.

<!-- gh-comment-id:2106894309 --> @Omegaviv commented on GitHub (May 13, 2024): okay I will create a issue on AppFlowy-plugin repository and push the changes there.
Author
Owner

@Xazin commented on GitHub (May 13, 2024):

okay I will create a issue on AppFlowy-plugin repository and push the changes there.

Thanks a lot, feel free to DM me or reach out on our discord if you have questions or if I can assist you with anything.

<!-- gh-comment-id:2107244386 --> @Xazin commented on GitHub (May 13, 2024): > okay I will create a issue on AppFlowy-plugin repository and push the changes there. Thanks a lot, feel free to DM me or reach out on our discord if you have questions or if I can assist you with anything.
Author
Owner

@annieappflowy commented on GitHub (Nov 28, 2024):

Supported

<!-- gh-comment-id:2505450569 --> @annieappflowy commented on GitHub (Nov 28, 2024): Supported
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#2301
No description provided.