Closed enkhjile closed 1 week ago
Thanks for your contributions. I did a bit of experiments and seems like only the input to File
, needs unescaped values so please revert changes to other places, also could you run cargo fmt
inside tooling/bundler
?
@amrbashir
Thanks for your feedback. I have reverted the changes to the installer.nsi
, except for the File
sections, and have run cargo fmt
.
Registering a global escape function that replaces
$
with$$
in Handlebars causes the build step to fail when resources contain$
in their names, because NSIS commands likeFile /a
cannot resolve the escaped paths. #9657I've added a helper that unescapes
$$
back to$
and modified the corresponding resource expression ininstaller.nsi
to use this helper.If there are better solutions, I'd be happy to implement them.