We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
metadata
It would be great for returned metadata to mark the initial custom element as the entry point, which can be helpful for more app like usages of WCC.
For example
const { metadata } = await renderToString(new URL('./src/pages/home.js', import.meta.url)); /* * { * metadata: [ * 'wcc-home': { instanceName: 'HomePage', moduleURL: [URL], entry: true }, * 'wcc-footer': { instanceName: 'Footer', moduleURL: [URL] }, * 'wcc-header': { instanceName: 'Header', moduleURL: [URL] }, * 'wcc-navigation': { instanceName: 'Navigation', moduleURL: [URL] } * ] * } *
However, if there is no tagName provided, like for a layout route or page, the next level of custom elements should be used instead.
tagName
The text was updated successfully, but these errors were encountered:
thescientist13
Successfully merging a pull request may close this issue.
Type of Change
Summary
It would be great for returned metadata to mark the initial custom element as the entry point, which can be helpful for more app like usages of WCC.
Details
For example
However, if there is no
tagName
provided, like for a layout route or page, the next level of custom elements should be used instead.The text was updated successfully, but these errors were encountered: