I have a "Render: twig" action which includes an inline Javascript snippet. I know that may not look like best practice, however sometimes quick and simple solutions are needed.
The included inline JS looks like this:
<script>
document.querySelector('[name="my_field"]').addEventListener('change', e => {
const u = new URL(window.location);
u.searchParams.set('my_field', e.target.value);
window.location.href = u;
});
</script>
The problem is that the produced output of the template looks like this:
<script>
document.querySelector('').addEventListener('change', e => {
const u = new URL(window.location);
u.searchParams.set('my_field', e.target.value);
window.location.href = u;
});
</script>
The query selector argument was interpreted as token and got replaced by an empty string.
What's the best way to deal with this?
Active
3.0
Miscellaneous
We've had an issue at 💬 An option to enable tokens support Fixed where we ended up using 2 tokens that contain the opening and closing brackets as their content. Maybe not the most ideal solution, but it is working.
Thanks for the link to the other issue. Using A token for the opening bracket and another one for the closing one may indeed a valid trick to work with.