Customizing tiddler names doesn't support constructor filter expressions, does it?

1

When configuring $:/config/FileSystemPaths, if I use a tag to filter, it categorizes correctly. If I include a constructor filter expression, such as enlist, it fails to categorize correctly. Is this a bug?

this can’t categproze cprrectly.

[enlist{Forge-config}addprefix[forgeForge/]]
2

How does your Forg-config content look like?

3

just list some tiddlers,like this

[[$:/config/FileSystemPaths]] homepage-Control-Panel-config Forge-config-fitler light-or-dark-mode-palette [[$:/config/NewTiddler/Tags]] [[$:/GitHub/Repo]] [[$:/palette]] [[$:/SiteSubtitle]] [[$:/SiteTitle]] Forge-config-siteTitle [[$:/config/NewJournal/Tags]]
4

I think this is key point.

5

Does this info from Saq resolve your issue?

6

I’ve changed my approach. I’ve now added specific fields to all these tiddlers, and I’m using those fields to filter them, which results in the correct categorization. The Saq response explained part of this, but I think more clarification is needed. This information should be written in the documentation; otherwise, other issues might arise, such as the problem with the tagging filter expression mentioned above.

7

I did add this thread to the existing GitHub issue: [BUG] User Defined Filter Operators Using Functions Do Not Work When Used in Filter Expression in FileSystemPaths · Issue #8561 · TiddlyWiki/TiddlyWiki5 · GitHub
So it won’t be forgotten.