-
-
Notifications
You must be signed in to change notification settings - Fork 3
fix: formatting for text nodes #128
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
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Signed-off-by: Manuel <30698007+manuel3108@users.noreply.github.com>
🦋 Changeset detectedLatest commit: e5fb9ef The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
…ho91/js-ast into fix/formatting-for-text-nodes
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
commit: |
|
`; | ||
const node = parse_and_extract<AST.Fragment>(code, "Fragment"); | ||
expect(printFragment(node).code).toMatchInlineSnapshot(` | ||
"{#snippet template({ children, ...args }: Args<typeof Story>, context: StoryContext<typeof Story>)} | ||
" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Intentional. I'm not touching whitespace characters if we're to use printFragment()
directly.
It's only being removed from the printRoot()
and above.
I currently have no clue at the codebase, thus decided to add some failing tests in the meantime. Happy to work on it if you give me a few hints.
Noticed while trying to include
svelte-ast-print
intosv
for a POC