Customizing Quasar styling - What's considered part of the public API?

[janzeppenfeld]

Hi, we are considering using Quasar for a new project in a company and also compare it to several other UI libraries out there. We saw that there are multiple ways to customize Quasar, which is important to us, because we heavily want to customize Quasar and want to use Design Tokens on top of it:

• Overriding some predefined SCSS variables for a limited number of components
• Using component-specific JS properties
• Overriding the component-specific CSS classes, which use BEM notation, themselves

I guess, that the JS properties and the exposed SCSS variables can be considered as part of the public API, so that a breaking change to them would lead to a major version update.

Compared to some other UI libraries, Quasar doesn't explicitly list the component-specific CSS classes in the documentation. The only hint I could find is a statement of @rstoenescu here, but I can't really say, if that means, that you consider the component-specific CSS classes as part of the public API.

So all in all, I have the following questions:

• Do you consider the JS properties and the exposed SCSS variables of components as part of the public API?
• Do you consider the component-specific CSS classes as part of the public API?
• Will breaking changes to the public API lead to major version change?

Thank you 😃