Generate IDs for headers added through Vue components or raw HTML
See original GitHub issueHi,
I almost finished my lib docs and now I am refactoring demos and I want to put demo section links in my custom card.
How can I convert my h2
tag like markdown-it
tag so it can get anchor based on its name.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Using Vue.js slots to pass HTML content to components
Learn how using Vue.js slots can be an efficient solution for passing down template code from one component to another.
Read more >Vue JS - dynamically created components rendered with ...
I'm creating the Test components dynamically per each relevant cell and assigning it to the relevant row cell. since I've defined the columns ......
Read more >Built-in Directives - Vue.js
In Single-File Components, scoped styles will not apply to content inside v-html , because that HTML is not processed by Vue's template compiler....
Read more >Composing with Components | Vue GWT - GitHub Pages
Components are one of the most powerful features of Vue. They help you extend basic HTML elements to encapsulate reusable code. At a...
Read more >Table | Components - BootstrapVue
The key is also used for generating the custom data rendering and custom header and footer slot names. label, String, Appears in the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You probably should publish your docs without that. It’s currently on low priority and frankly I’m unsure how to handle that unless generating outline completely on client side.
Great! It looks promising. I guess this is now a feature request rather than a question.
Shall we keep it open?
Moreover, this issue issues needs to resolve two feature request hence it might take longer. I probabaly release the lib next week. May I know should I want to move on without this feauture?
Thanks.