[BUG] RSOE from decodebase64

[twMat]

Describe the bug

RSOE from not-sure-what-to-call-this

text: {{{ [[http://tiddlywiki.com]decodebase64[]] }}}

Uncaught URIError: URI malformed

Expected behavior

No response

To Reproduce

type the above into a tiddler on e.g tiddlywiki.com and save the tiddler → error

Screenshots

No response

TiddlyWiki Configuration

tw 5.3.5 (e.g on tiddlywiki.com)
win11, brave browser

Additional context

No response

[Leilei332]

IMO the error should be displayed in the result of the filter expression instead of showing RSOE, like this:

After all, I think we should implement "exception handling" for the operator to catch the error.

[twMat]

@Leilei332
Do you mean that a {{{ filtered transclusion }}} by itself should alert about errors? (because the OP has nothing to do with the search mechanism). Interesting!

[Leilei332]

It is up to filter expression to alert about errors, and Tiddlywiki already supports displaying an error message when the filter expression syntax is wrong.

The advanced search page is used to test the filter expression, and RSOE also appears when you type [[http://tiddlywiki.com]decodebase64[]] in the Filter tab.

IMO the error is caused by inappropriate usage of the decodebase64 operator. I think we can display error message like Filter error: URI malformed when the exception is caught.

[Jermolene]

Hi @twMat @Leilei332 we definitely don't want an RSOE. An error message as the response would indeed appear to be the best way forward. I would welcome a PR