Closed Hrxn closed 1 year ago
It has been like this, conversions raising an exception when applied to anything but the expected type, since forever.
You should just use {description|''!t}
to make sure t
gets a string.
I just realized that this has been the setting in my config for "filename"
, and I've downloaded a bunch of gigs these days and it seemed to be working just fine?
"{num:?/./>04}{gallery:?/./[:11]}{date:%Y-%m-%d}.{tags|'Untagged':?/./J_/}{description[:80]!t:?/./R.//}{filename}.{width}x{height}.{extension}"
This means I haven't reliably reproduced it, apparently..
Anyway, with the alternative you suggested:
"{num:?/./>04}{gallery:?/./[:11]}{date:%Y-%m-%d}.{tags|'Untagged':?/./J_/}{description[:80]|''!t:?/./R.//}{filename}.{width}x{height}.{extension}"
I think I'm gonna close this
Just found this..
Proof that it's working if I remove the
!t
conversion specifier:Well I guess it is basically expected in this case, because this example on redgifs (a SFW one basically.. I mean something you can also see on Instagram, I'd say) does not have a
description
, but some clips there now have..But maybe it shouldn't fail even without a value for
description
?