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
Currently, we reformat HTML/JS after running it through the tool. This can lead to a few issues:
JS
The formatting may end up different from the source file, e.g. in the case of indentation.
Before:
exportdefaultclassFooextendsLightningElement{// Public
@apititle;}
After:
exportdefaultclassFooextendsLightningElement{staticrenderMode="light";// Public
@apititle;}
(Note the changed indentation.)
HTML
Before:
<some-componentfoo></some-component>
After:
<some-componentfoo=""></some-component>
This is equivalent code per HTML semantics, but in the case of some-component it might actually treat the two differently. So this could change the behavior. Actually getAttribute/hasAttribute returns the same thing in both cases, so it's strictly equivalent.
We also transform things like SVG <path /> into <path></path>. (Equivalent, but potentially unwanted.)
CSS
I'm not aware of any cases where we change formatting/indentation, but maybe we do.
The text was updated successfully, but these errors were encountered:
Currently, we reformat HTML/JS after running it through the tool. This can lead to a few issues:
JS
The formatting may end up different from the source file, e.g. in the case of indentation.
Before:
After:
(Note the changed indentation.)
HTML
Before:
After:
This is equivalent code per HTML semantics,
but in the case ofActuallysome-component
it might actually treat the two differently. So this could change the behavior.getAttribute
/hasAttribute
returns the same thing in both cases, so it's strictly equivalent.We also transform things like SVG
<path />
into<path></path>
. (Equivalent, but potentially unwanted.)CSS
I'm not aware of any cases where we change formatting/indentation, but maybe we do.
The text was updated successfully, but these errors were encountered: