Embedded base should have equal content to non-embedded base

Feature requests
1

Use case or problem

I created a folder to collect academic journals with a base folder note. As I plan to collect all entries in this folder, I just created a filter that collects all files in that folder: this.file.folder == file.folder AND file.ext == “md” (the latter excludes the base).

This works great and is a very quick way to create a base of things.

However, when embedding this base in any other folder, the filter now interprets this as the file that the base is embedded into and no longer as the original base.

Proposed solution

Embedded bases should not take the embedded context as their context for filtering, or at least, the variable thisshould always reference the base and not any embed-sourroundings.

Current workaround (optional)

Hard-coding folder names into filters, which really makes them prone to breakage. If folders are renamed, all bases referencing those folders need to be refactored.

2

Addition: Creating a new file should also respect the filter, meaning that new files will be created in the base directory.

The same way that static path filters are treated: Bases: Honour the file path filter when creating a new file from a base view

3

I disagree.

.this referring to the note a base is embedded in rather than the base itself allows for a lot of useful functions. With your proposed solution, you would need one base (or at least base views) for each folder where you want to list files. With the current way, you can create a single base view and embed it in multiple folders to list all folder files. This is much more useful in my opinion.

It would be nice to have a similar variable, like .this, to reference the base file itself, but it should definitely not change the current behaviour.

4

Fair point.

In that case, it would be super helpful to add a variable e.g. base to allow some for of self-reference to the .base file and its position.

1 Like