Skip to content
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

Fix vscode custom data tag name #593

Merged
merged 1 commit into from Nov 22, 2021
Merged

Fix vscode custom data tag name #593

merged 1 commit into from Nov 22, 2021

Conversation

kt0
Copy link
Contributor

@kt0 kt0 commented Nov 22, 2021

I also wanted to add url and description but no data wasn't available from custom-elements.json, I thought about useing docs/components/{component}.md before ## Examples but that's unpredictable and probably a hell to maintain

@vercel
Copy link

vercel bot commented Nov 22, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/shoelace/shoelace/GpmCeqrD2QaT6ZycjnpumjtYeVnk
✅ Preview: https://shoelace-git-fork-kt0-next-shoelace.vercel.app

@claviska claviska merged commit 9afb32f into shoelace-style:next Nov 22, 2021
@claviska
Copy link
Member

Agree. I'd eventually like to move from Docsify to an 11ty site that supports front matter in its markdown files. That will make this easier to do.

Thanks for catching this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants