Access to sass files from npm/yarn package

[soullivaneuh]

If I add the package:

yarn add swagger-ui

I only have this:

I need the sass file to override the variables. Could you please add this possibility?

[soullivaneuh]

Current workaround: Adding the tar.gz of the release:

yarn add https://github.com/swagger-api/swagger-ui/archive/v3.19.4.tar.gz

But you wont get any update anymore.

[soullivaneuh]

Also, a documentation part about how to use sass files would be great. 👍

[soullivaneuh]

Any feedback about this issue? 🤔

[shockey]

Yep! We've avoided this until now because our SASS variable strategy (and CSS patterns in general) aren't in great shape, and we don't want folks to start relying on what naming conventions we're using at the moment (related: #4460).

Would exposing SCSS in the module be acceptable if we provided it outside of our semantic versioning contract, meaning that future minor and patch versions could break SCSS variable names and values?

[soullivaneuh]

if we provided it outside of our semantic versioning contract, meaning that future minor and patch versions could break SCSS variable names and values?

@shockey It would be better to have BC rules on it as we use it for overriding.

However, if this is too cumbersome for you, this may be acceptable if a warning message about that is present on the README. 👍

[soullivaneuh]

@shockey Friendly ping. :-)

[jpoehnelt]

Would exposing SCSS in the module be acceptable if we provided it outside of our semantic versioning contract, meaning that future minor and patch versions could break SCSS variable names and values?

Absolutely. Right now, I'll be seeking out a workaround that is more likely to break between versions.

[Drafter500]

This is highly needed. I see it as the only normal way to co customise the theme