Lookup: Support 'archive' sort ordering for archiving functionality

nickolay-kondratyev commented 2 years ago

Please select if your request is either something new or an enhancement

[x] Enhancement of an existing Feature.
[ ] Request of a new feature.

Please select the area your request applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace - VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[x] Lookup - Dendron's Lookup Command
[ ] Views - Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema - Dendron Schemas
[ ] Pod - Data import from / export to Dendron
[ ] Publish - External Site Publish
[ ] Markdown - Markdown features, such as syntax support and features

Is your feature request related to a problem? Please describe

Currently there isn't an archiving capability.

Describe the solution you'd like

To be able to reach archived notes but for archived notes to not clutter the top results of the lookup.

A simple solution to this problem can be adding sort order prior to sort order of the score (https://github.com/dendronhq/dendron/blob/master/packages/common-all/src/fuse.ts#L317-L324) against some archive signaling mechanism.

A suggested signaling mechanism is to have archive be part of the note name (to allow utilization of other refactoring tooling such as being able to archive a hierarchy by using Refactor Hierarchy command).

It would be nice to not limit archive note naming to only the beginning meaning to allow support for:

foo.bar.baz -> foo.archive.bar.baz (this way a sub hierarchy can be archived, but main hierarchy could have other un-archived children).

However, even supporting foo.bar.baz -> archive.foo.bar.baz would be super helpful for organizational lookup.

With this addition to sorting if someone wants to find the archived notes they could still reach them an even filter out the non archived notes by just typing archive into the lookup query.

Describe alternatives you've considered

Approach 1: Trying to manually change the update time on the note. (which gets overriden)
Approach 2: Attempting to set initial value for note lookup as
```
{
    "key": "cmd+l",
    "command": "dendron.lookupNote",
    "args": {
        "initialValue": "!archive "
    }
},
```
Setting the initial value has the nuisance of having the !archive selected which requires hitting the arrow key (which quite far from the home row while navigating quickly).

Additional context

aleksey-rowan commented 2 years ago

Hey, @nickolay-kondratyev, there was an issue before that referred to a similar concept--subtree hoisting (where you filter the tree and restrict the lookup to a certain hierarchy):

https://github.com/dendronhq/dendron/issues/664

What you suggesting is the opposite of hoisting (de-hoisting? :)) where certain hierarchies are excluded from the lookup, but I think the general concept is the same--focusing on specific parts of your vault.

aleksey-rowan commented 2 years ago

This issue is featured in this week's round of CROP voting.

dendronhq / dendron