DB version: inline tags?

Feedback Feature Requests
1

Hello everyone!

In the development builds of the DB version, it looks like the #tags are automatically moved to the right of the block, like this:

Meeting with [[John]] for [[Project B]] ______________________________ #meeting

In the current version of Logseq, however, I love using tags as part of the natural language, like this:

#meeting with [[John]] for [[Project B]]

It has less redundancy and feels way more natural to write.

So, my suggestion for the DB version would be to at least have an option to keep the tags “in line” with the text, while still working as intended (turning a block into an instance of that tag).

What do you think?
Do you use this “natural language” approach?
Do you think it would make sense to make it possible in the DB version?

2

Inline tags have been implemented in Logseq DB some alpha versions ago (you can decide per tag where it shows), so I’ll close this request.

For now, please don’t post feature requests for Logseq DB as it’s still in development. We have a limited group of alpha testers to give us feedback, as it’s impossible for our small dev team to keep up if everybody is going to give feedback at this stage. And in this particular case, this feature has already been added.

1 Like
3

That’s great to know! I had missed that feature.
Edit: I can’t seem to find that option in the test instance (only one to choose where properties will appear), so I’ll wait this out and see how the final version works.

Noted! :blush:

1 Like
4

I’ll ask the devs to include in the documentation how to change the appearance of tags. You can find the early docs here: docs/db-version.md at feat/db · logseq/docs · GitHub

2 Likes
5

Hijacking this thread to suggest that a link to db-version-changes.md be posted on docs.logseq.com, preferably on the front page (#contents) of the official documentation.

I have been looking for detailed information about upcoming changes, but was not aware of the info on GitHub until now. I’m sure there are many others like me.

2 Likes
6

Maybe the forum should have a “DB-related chat” category, for all discussions about that?

With a big disclaimer explaining that it shouldn’t be used for feature requests and bug reports etc

Seems inevitable that people will want to keep talking/asking about it… Might as well put a fence around it :slight_smile:

Just a suggestion

1 Like
7

Logseq DB is still in closed alpha. Only once Logseq DB is stable enough for general use will we merge that documentation with docs.logseq.com. The devs really cannot handle more feedback at the moment, so promoting an unstable Logseq DB version via the docs is just asking for trouble.

Logseq DB is in closed alpha for a reason. With several hundreds of alpha testers, the devs already have trouble keeping up with all feedback and bug reports. So we’re not going to open a forum section about Logseq DB as too much is still changing and the devs would not be able to post there anyway.

Of course you’re free to discuss Logseq DB anywhere on this forum (some are already doing that in General), but if we’d open a subforum for it that could give people the idea the devs will be active there as well. For now, they only have enough mental bandwidth to give the alpha tester group full attention.

I’m closing this thread now before it gets hijacked more.

1 Like