The embedded <style scoped> element continues to function as usual and expected.
Combinations of styles are possible; all styles found (embedded css/scss, external scss file, and an external css file) are concatenated into the final scopedCss string.
I've tried to replicate the existing approach to parsing the template as much as possible so as to make this change cohere to the rest of the codebase as much as possible. Let me know if I can improve on any aspect!
This change adds behaviour to look for and parse an optional css and scss file as part of the component template.
File structure such as the following is then possible, allowing full segregation of presenter logic, markup/view logic, and styling:
The embedded
<style scoped>
element continues to function as usual and expected.Combinations of styles are possible; all styles found (embedded css/scss, external scss file, and an external css file) are concatenated into the final
scopedCss
string.I've tried to replicate the existing approach to parsing the template as much as possible so as to make this change cohere to the rest of the codebase as much as possible. Let me know if I can improve on any aspect!