Migrating from MD to DB with inline tags

As per DB version: inline tags? I’m wondering about the potential eventual migration from MD to DB. In the case of my graph I think I only really face the issue of inline tags.

As a test, I imported my graph into test.logseq.com and generally things are working quite well. The only thing I noticed is that, even when I uncheck ‘Remove inline tags’

I end up with end of line tags unless they were surrounded by double brackets. For example, a test graph with:

- Testing an #inline-tag for import to #db
- Testing an #[[Inline Tag]] for import to #[[DB]]

Results in:

Is there a way to preserve the inline tags that exist without the brackets?

2 Likes

I’m also interested in this.

In my previous post the reply was that inline tags had been implemented as a per-tag property. I’m not totally sure how that works, though, and didn’t research it further.

Does anyone from the team have any tips here? I actually feel, in my case, I could fairly easily just run a regex to replace all the unbracketed inline tags, but was just wondering if there were any official recommendations especially since an actual inline tag on the DB version doesn’t seem to create/require the brackets? (cmd+enter just creates the inline tag and an MD export doesn’t contain any extra brackets)

@danzu sorry to ping you here as I don’t know who I’m meant to reach out to - but just curious if anyone had any tips - eg, is this a bug or is this expected and are we meant to try to format things differently for a cleaner import? eg with this simple test case:

The end-of-the-line position for tags is the default behavior

Thank you, my question was more though, is there a reason why a line like:

- Test of an #inline-tag for import to #db

Doesn’t import those as inline tags but does if they are wrapped in brackets?

1 Like

May I ask below the Remove inline tag checkbox, it would be helpful to have another checkbox for Convert all tags to pages and the expected result would be all # will be wrapped in []