-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Wrongly formatted literal line #52
Comments
Two issues here:
|
I couldn't reproduce the issue :( https://github.com/prettier/plugin-pug/pull/57/files Maybe I need more content to test |
this is minimal example: div
a(href="")
h6 A
| !{veranstaltung.renderedPresseText()} |
Ja! Nun kann ich es reproduzieren 😉 |
Das freut! |
That has been the show stopper for today's pleasure! |
Thats why I want to reflect the other things only as a workaround
|
Go for it
… Am 04.01.2020 um 18:28 schrieb Shinigami ***@***.***>:
Thats why I want to reflect the other things only as a workaround
it's better code with the workaround
it's not that urgent like this issue
I can release the next version in the next few minutes :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#52?email_source=notifications&email_token=AADOBFANZBUDRIN7UD2GUB3Q4DBM3A5CNFSM4KCWASJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIC4KIA#issuecomment-570803488>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADOBFCBYTBCBFH6DWEGOELQ4DBM3ANCNFSM4KCWASJA>.
|
Could you give me a GO for these "documentations"? |
For #53 only the workaround with template string works for me. Better remove the other proposal: input(onClick="methodname('" + variable + "', this)") You can check it out, it will also transform to a non working variant. |
#54 is OK |
Is it because you are forced to double quotes in this place? |
Nevermind... I see 😒 OK this is a problem, but I would want to work on it later |
transforms to |
| !{variableWithHtmlString}
is formatted to
!{variableWithHtmlString}
Breaks rendering
The text was updated successfully, but these errors were encountered: