-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
[BUG] [Formatter] Formating of {% set = .. %} generate unparsable result for Jina2 #682
Closed
3 tasks done
Labels
Comments
Thanks, I will make quoted keys the default if Jinja requires it. This option was for jinja/njk so we will follow their lead :) |
christopherpickering
added a commit
that referenced
this issue
Jun 2, 2023
…t/function formatting closes #682
I also added flags to disable set/function formatting in case other issues come up and I cannot resolve quickly. |
2 tasks
christopherpickering
pushed a commit
that referenced
this issue
Jun 2, 2023
## [1.30.2](v1.30.1...v1.30.2) (2023-06-02) ### Bug Fixes * **formatter:** added quotes to json keys, added option to disable set/function formatting ([6f7df03](6f7df03)), closes [#682](#682)
🎉 This issue has been resolved in version 1.30.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System Info
Issue
Formating
Output
The indentation is fixed, but the quotes around
sPaging
are required for Jinja2.This changes seams to be introduce by 85aca4c
I don't see an option to disable that behavior either.
The text was updated successfully, but these errors were encountered: