You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for reporting this issue. I believe the surface formatter shouldn't touch anything inside <style> as we don't want to keep a full-featured css parser and formatter inside Surface. We should treat it just like a macro component and ignore any of its content. Then you could probably set up your own formatter/linter, something like Prettier to do that job for you.
@paulstatezny I believe the fix would be to add a clause for stylehere, right?
Activity
paulstatezny commentedon Mar 25, 2024
PRs are welcome :)
msaraiva commentedon Mar 26, 2024
Hey @zkat!
Thanks for reporting this issue. I believe the surface formatter shouldn't touch anything inside
<style>as we don't want to keep a full-featured css parser and formatter inside Surface. We should treat it just like a macro component and ignore any of its content. Then you could probably set up your own formatter/linter, something like Prettier to do that job for you.@paulstatezny I believe the fix would be to add a clause for
stylehere, right?paulstatezny commentedon Mar 26, 2024
@msaraiva Yes, adding a clause there would prevent the formatter from modifying the contents of
<style>tags.