Allow multiple content classes

[mstenquist]

I noticed an issue when vex.baseClassNames.content was set to a string containing multiple classes.

For example...

vex.baseClassNames.content = 'vex-content' (works fine)

vs.

vex.baseClassNames.content = 'vex-content vex-content-auto hs-modal' (breaks)

The culprit was $(@).parents(".#{vex.baseClassNames.content}") which tries to form a selector '.vex-content vex-content-auto hs-modal' Needless to say, this doesn't work.

The solution was to add a utility method getBaseClassesAsSelector to vex. It's job is to simply split/join and return our properly formatted selector .vex-content.vex-content-auto.hs-modal

@timmfin @zackbloom @gusvargas @b-ash

[b-ash]

⛵

[adamschwartz]

Hey @mstenquist, thanks so much for this!

I think this is a great suggestion, but your particular implementation strikes me as a little strange. Rather than have the method getBaseClassesAsSelector return the content selector specifically, I think it would make more sense to pass in base class and have it return the selector. That way this could be used for more classes than just vex.baseClassNames.content.

Also, I think the name would make more sense as getSelectorFromBaseClass. So altogether it would look something like this:

vex.getSelectorFromBaseClass(vex.baseClassNames.content)

[mstenquist]

@adamschwartz Ooo.. I like that. Thanks for the feedback.