generate copy without wikilinks #1365

hereistheusername · 2024-06-21T12:52:20Z

Abstract

As mentioned in #1353 , #1319, and #791, many people got difficulties when working with other tools that don't support wikilinks. To tackle this problem, I add a function to convert link format.

Further Explanation

Implementation

Refactoring the MarkdownLink.createUpdateLinkEdit, the convertLinkFormat function resolves links based the note containing it and its workspace and combine components properly.

User Interface

4 commands:

foam-vscode.convert-wikilink-to-markdownlink-inplace
foam-vscode.convert-markdownlink-to-wikilink-inplace
foam-vscode.convert-wikilink-to-markdownlink-in-copy
foam-vscode.convert-markdownlink-to-wikilink-in-copy

to meets users' different needs.

Thanks to @riccardoferretti help.

riccardoferretti

Thanks for looking into this.
At a high level, have you looked at MarkdownLink.createUpdateLinkEdit? it should do most of what you need in terms of refactoring.

Can you also tell me your thinking about having this as a command vs a formatting setting (kinda like using wikilink definitions)?
I would like to understand the feature from the POV of the user: is this about having a documenta that is always md compatible (in which case the transformation would happen on save), or is it about being able to export the knowledge base for e.g. a static site generator (in which case do we need a command for that?), or about exporting a single file (which is what you are implementing IIUC) - thoughts?

packages/foam-vscode/src/features/commands/generate-standalone-note.ts

riccardoferretti · 2024-06-21T14:15:06Z

packages/foam-vscode/src/core/janitor/generate-mdlinks.ts

+    }
+    return '';
+  }
+  public toMarkdownLink(


You probably can reuse the mechanisms available in MarkdownLink to achieve the same in a more integrated way

hereistheusername · 2024-06-21T15:53:47Z

Thanks for looking into this. At a high level, have you looked at MarkdownLink.createUpdateLinkEdit? it should do most of what you need in terms of refactoring.

Can you also tell me your thinking about having this as a command vs a formatting setting (kinda like using wikilink definitions)? I would like to understand the feature from the POV of the user: is this about having a documenta that is always md compatible (in which case the transformation would happen on save), or is it about being able to export the knowledge base for e.g. a static site generator (in which case do we need a command for that?), or about exporting a single file (which is what you are implementing IIUC) - thoughts?

Thank you for the quick review. Currently, I ran into a bug that it cannot resolve the wikilink to embeded images URI through workspace.resolveLink(resource, link). I am working on it and I'll also check the MarkdownLink.createUpdateLinkEdit.

The reason for doing this is wikilinks are more flexible, which leaves the workspace to manage the resource path. For example, I usually start with a single draft, and with more resources are added in the idea gets mature. At some point, I would like to re-organize or archive a group of ideas. If files are linked by wikilinks, I can move them freely. So, I think keeping linkages as wikilink would be benefit for PKM. However, if choosing format, there could be chance that links get broken, and it will need efforts to fix them.

In my imagination, users are recommanded to use wikilinks and only need to generate a standalone copy when they want to "export" their ideas. After that, those copies can be wiped out, by manually or scripts. Single file is not neccessary. Providing options to export a list of selected files or a whole directory would be helpful.

riccardoferretti

PR is looking good, I left a few comments. Thanks for the explanation around the rationale, we are aligned and this feels like it's pushing things in the right direction

packages/foam-vscode/src/core/janitor/convert-links-format.ts

riccardoferretti · 2024-06-24T10:31:59Z

packages/foam-vscode/src/core/janitor/convert-links-format.ts

+  const targetRes = workspace.find(targetUri);
+  let relativeUri = targetRes.uri.relativeTo(resource.uri.getDirectory());
+
+  if (targetFormat === 'wikilink') {
+    /* remove extension if possible, then get the basename to prevent from filename conflict */
+    if (relativeUri.path.endsWith(workspace.defaultExtension)) {
+      relativeUri = relativeUri.changeExtension('*', '');
+    }
+    target = relativeUri.getBasename();
+
+    return {
+      newText: `${embed}[[${target}${sectionDivider}${section}${aliasDivider}${alias}]]`,
+      range: link.range,
+    };
+  }
+
+  if (targetFormat === 'link') {
+    /* if alias is empty, construct one as target#section */
+    if (alias === '') {
+      /* in page anchor have no filename */
+      if (relativeUri.getBasename() === resource.uri.getBasename()) {
+        target = '';
+      }
+      alias = `${target}${sectionDivider}${section}`;
+    }
+
+    /* construct url */
+    let url = relativeUri.path;
+    /* in page anchor have no filename */
+    if (relativeUri.getBasename() === resource.uri.getBasename()) {
+      url = '';
+    }
+    if (sectionDivider === '#') {
+      url = `${url}${sectionDivider}${section}`;
+    }
+    if (url.indexOf(' ') > 0) {
+      url = `<${url}>`;
+    }
+
+    /* if it's originally an embeded note, the markdown link shouldn't be embeded */
+    if (embed && targetRes.type === 'note') {
+      embed = '';
+    }
+    return {
+      newText: `${embed}[${alias}](${url})`,
+      range: link.range,
+    };
+  }


I haven't tested it locally, but I wonder if you could be able to replace this whole section with

const newLink = {...link, type: targetType} const edit = MarkdownLink.createUpdateLinkEdit(newLink)

I think it's impossible. The first line of MarkdownLink.createUpdateLinkEdit is

const { target, section, alias } = MarkdownLink.analyzeLink(link);

which extracts three components via regex from link.rawText based on link.type. If the pattern doesn't match, three of them may not be extracted correctly.

Moreover, when dealing with conversion from wikilink to link, we have to retrieve the relative path to target, which is usually a basename in wikilink's rawText. Therefore, we must have workspace and note: Resource | URI.

Yeah, good point. Basically instead increateUpdateLinkEdit we need to add type?: 'wikilink' | 'link' to the delta parameter, and take it from there. Does that sound good?

Here is one possible version. I added type and isEmbed to the delta, which slightly affacts how createUpdateLinkEdit composes newText. Please check it.

differ to current code
branch

packages/foam-vscode/src/features/commands/convert-links-format-in-note.ts

riccardoferretti · 2024-06-24T10:39:14Z

packages/foam-vscode/src/features/commands/convert-links-format-in-note.ts

+/**
+ * convert links based on its workspace and the note containing it.
+ * Changes happen in a copy
+ * 1. prepare a copy file, and makt it the activeTextEditor


riccardoferretti · 2024-06-24T10:41:27Z

packages/foam-vscode/src/features/commands/convert-links-format-in-note.ts

+  const resource = fParser.parse(fromVsCodeUri(doc.uri), text);
+
+  const textReplaceArr = resource.links
+    .filter(link => link.type === convertOption.from)


(note: in my proposed approach, this check would be link.type !== convertOption.to)

hereistheusername added 4 commits June 21, 2024 18:12

inseart new test file

60b4adf

add generate standalone note command

bab6cd7

vscode cmd configure

bcfde0e

fix embeded wikilinks

76ed1ad

riccardoferretti reviewed Jun 21, 2024

View reviewed changes

hereistheusername added 3 commits June 23, 2024 22:38

refactor convertLinksFormat function & add 4 user command interfaces

07702c2

cleanup

62f458e

add comments

0aefd72

hereistheusername marked this pull request as ready for review June 23, 2024 15:19

riccardoferretti reviewed Jun 24, 2024

View reviewed changes

hereistheusername added 3 commits June 24, 2024 21:02

change user interface

2e350d7

del outdated comments

08451f1

fix typo

18dbbb5

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

generate copy without wikilinks #1365

generate copy without wikilinks #1365

hereistheusername commented Jun 21, 2024 •

edited

Loading

riccardoferretti left a comment

riccardoferretti Jun 21, 2024

hereistheusername commented Jun 21, 2024

riccardoferretti left a comment

riccardoferretti Jun 24, 2024

hereistheusername Jun 24, 2024

riccardoferretti Jun 26, 2024

hereistheusername Jun 28, 2024 •

edited

Loading

riccardoferretti Jun 24, 2024

riccardoferretti Jun 24, 2024

generate copy without wikilinks #1365

Are you sure you want to change the base?

generate copy without wikilinks #1365

Conversation

hereistheusername commented Jun 21, 2024 • edited Loading

Abstract

Further Explanation

Implementation

User Interface

riccardoferretti left a comment

Choose a reason for hiding this comment

riccardoferretti Jun 21, 2024

Choose a reason for hiding this comment

hereistheusername commented Jun 21, 2024

riccardoferretti left a comment

Choose a reason for hiding this comment

riccardoferretti Jun 24, 2024

Choose a reason for hiding this comment

hereistheusername Jun 24, 2024

Choose a reason for hiding this comment

riccardoferretti Jun 26, 2024

Choose a reason for hiding this comment

hereistheusername Jun 28, 2024 • edited Loading

Choose a reason for hiding this comment

riccardoferretti Jun 24, 2024

Choose a reason for hiding this comment

riccardoferretti Jun 24, 2024

Choose a reason for hiding this comment

hereistheusername commented Jun 21, 2024 •

edited

Loading

hereistheusername Jun 28, 2024 •

edited

Loading