The latest updates on your projects. Learn more about Vercel for Git ↗︎

Hi @Koooooo-7 , thanks very much for taking a go at this! I've made a little test site using the PR Preview:
https://paulhibbitts.github.io/docsify-v5-multiple-value-config-test/#/multiple-values-example

An image with two classes worked like a charm. Is this feature also expected to work for text links? I ask because with v5 there are now two classes for defining buttons, button + primary and button + secondary.

Hope I did everything with in my test page 🙂

PS - GitHub renders the page with the markup quite cleanly still: https://github.com/paulhibbitts/docsify-v5-multiple-value-config-test/blob/main/multiple-values-example.md

Hi @Koooooo-7 , thanks very much for taking a go at this! I've made a little test site using the PR Preview: https://paulhibbitts.github.io/docsify-v5-multiple-value-config-test/#/multiple-values-example

An image with two classes worked like a charm. Is this feature also expected to work for text links? I ask because with v5 there are now two classes for defining buttons, button + primary and button + secondary.

Yep, I think this should work either.

[logo-link](https://docsify.js.org/_media/icon.svg ':id=someCssId :class=someCssClass :target=_self :class=anotherCssClass :disabled')

Hope I did everything with in my test page 🙂

Your working as fast as the rocket shoot ! 🚀

Thats awesome @Koooooo-7 , this initial support for multiple classes is VERY useful 🙌🏻 Thank you!

Should we only allow class?

![logo](https://docsify.js.org/_media/icon.svg ‘:id=someCssId :id=id2’)

Should we only allow class?

![logo](https://docsify.js.org/_media/icon.svg ‘:id=someCssId :id=id2’)

Currently, in our scope, only class are necessary to supported multi values.
Technically, it allows all config to config as multi times/values.
It depends on what the attr made for. Such as the id, there make no sense to config 2 id.
And we could/have doc all configs how to config, and which configs support multi values to users.
(We don't have guideline to say we support id like #Title :id=id1 :id=id2 in our document)

Personally, I think it is okay cuz user needs follow the rules. and if the config not work as expected, they can be aware of that either.
The config validation (config non exist key, config invalid value, config key with multi values but the key does not support ..etc) we could make as another topic, if necessary.
WDYT?