-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] User Defined Filter Operators Using Functions Do Not Work When Used in Filter Expression in FileSystemPaths #8561
Comments
Globals are not available in the evaluation of file system paths. |
Is it true for |
kookma
changed the title
[BUG] Functions Does Not Work When Used as Filter Operator in FileSystemPaths
[BUG] User Defined Filter Operators Using Functions Do Not Work When Used in Filter Expression in FileSystemPaths
Aug 28, 2024
All global variables are not available when evaluating $:/config/FileSystemPaths |
Thank you for clarification! I keep this open as a hint for other potential users. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Filter expressions in
$:/config/FileSystemPaths
if use custom filter operators will not work.Expected behavior
I defined a custom function in a tiddler tagged with
$:/tags/Global
Then in the
$:/config/FileSystemPaths
I used a filter like belowIt not only does not work, but also makes none of other filter expression to run!
TiddlyWiki Configuration
The text was updated successfully, but these errors were encountered: