-
Notifications
You must be signed in to change notification settings - Fork 715
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
Second Parameter for unescape modifier not working #777
Comments
fyi: in my case I remove the utf-8 there as I didn't needed, but I thought I wanted to share this issue, if maybe somebody else stumbled across this. |
Definitely sounds like a bug to me! I'll look into it. |
wisskid
added a commit
that referenced
this issue
Aug 1, 2022
wisskid
added a commit
that referenced
this issue
Aug 1, 2022
wisskid
added a commit
that referenced
this issue
Aug 1, 2022
wisskid
added a commit
that referenced
this issue
Aug 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not sure if I'm doing it just wrong or if there is a bug in the unescape modifier
What I'm trying is something like this
This results in:
Looking into the code, I see that there is
$params[ 2 ] = "'{$params[ 2 ]}'";
- but somehow it is already in quotes.For
params[1]
it does a trim for"
and'
- why not forparams[2]
?On a side note, even if I not using it, but I tested it now while debugging this issue:
results in
so its not working
$encoding
is inside single quote.The text was updated successfully, but these errors were encountered: