-
Notifications
You must be signed in to change notification settings - Fork 1
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
Print slotted content within the assigned slot #2
Conversation
Replace prettier2 with prettier3
Upgrade to node.js version 20
…tted content into the assined slot
"typescript": "^5.4.3" | ||
}, | ||
"engines": { | ||
"node": ">=20", |
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.
@jwloka wir supporten nicht nur >= Node 20, oder?
Weil so, generieren wir den Verwendern immer eine Warning: https://docs.npmjs.com/cli/v10/configuring-npm/package-json#engines
Unless the user has set the [engine-strict config](https://docs.npmjs.com/cli/v10/using-npm/config#engine-strict) flag, this field is advisory only and will only produce warnings when your package is installed as a dependency.
src/renderToString.spec.ts
Outdated
slottedContent: "map-contents", | ||
} as any); | ||
|
||
expect(actual).toMatchInlineSnapshot(`""`); |
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.
Da ist wohl etwas zwischen den Commits kaputt gegangen.
expect(actual).toMatchInlineSnapshot(`""`); | |
expect(actual).toMatchInlineSnapshot(`" | |
<p> | |
EXPECTED | |
</p> | |
"`); |
Some test snapshots make it hard to understand what content is slotted into a particular slot. This PR provides a new rendering option 'slottedContent'. Use value "reveal-contents" to show slotted content in its original and its assigned (slotted) position. Use value "map-contents" to move the slotted nodes into the assigned slot.