-
Notifications
You must be signed in to change notification settings - Fork 36
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] max line width breaks ampscript code in assets #1248
Closed
2 tasks done
Milestone
Comments
JoernBerkefeld
added
bug
Something isn't working
c/asset
COMPONENT
NEW
not yet analyzed new issues get this label
labels
Apr 8, 2024
could be fixed by changing "files.associations": {
"*.html": "AMPscript"
},
"[html]": {
"editor.defaultFormatter": "FiB.beautyAmp"
}, that way, we no longer apply prettier settings but instead run beautyAmp on the code. tested this myself already and it seems to work |
JoernBerkefeld
added a commit
that referenced
this issue
May 22, 2024
JoernBerkefeld
added a commit
that referenced
this issue
May 22, 2024
it runs prettier on html but also formats ampscript
4 tasks
JoernBerkefeld
added a commit
that referenced
this issue
May 22, 2024
…make writing asset-test cases easier
JoernBerkefeld
added a commit
that referenced
this issue
May 22, 2024
JoernBerkefeld
added a commit
that referenced
this issue
May 22, 2024
…es easier; add amscript-language to recommended extensions for contributors
JoernBerkefeld
added a commit
that referenced
this issue
May 22, 2024
JoernBerkefeld
added a commit
that referenced
this issue
May 22, 2024
JoernBerkefeld
added a commit
that referenced
this issue
May 22, 2024
4 tasks
Closed by #1341. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
saw it happening with contentblockbyname which tends to have a very longer argument.
Expected Behavior
ampscript code does not get auto-line breaks applied
Steps To Reproduce
Version
6.0.2
Environment
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: