github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 17:28:26 -04:00
Code Issues Projects Releases Packages Wiki Activity

Explain rationale of HTML bracket formatting in HTML style guide. (#9629)

Browse source
This commit is contained in:
CJ Cenizal 2016-12-23 12:16:51 -08:00 • committed by GitHub
parent 018c3f4677
commit 045e654c15
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
style_guides/html_style_guide.md
View file

@ -3,9 +3,11 @@
## Multiple attribute values
When a node has multiple attributes, each attribute including the first should be on its own line with a single indent.
When an element has multiple attributes, each attribute including the first should be on its own line with a single indent.
This makes the attributes easier to scan and compare across similar elements.
The closing bracket should be on its own line. This allows attributes to be shuffled and edited without having to move the bracket around. It also makes it easier to scan vertically and match opening and closing brackets.
The closing bracket should be on its own line. This allows attributes to be shuffled and edited without having to move the bracket around. It also makes it easier to scan vertically and match opening and closing brackets. This format
is inspired by the positioning of the opening and closing parentheses in [Pug/Jade](https://pugjs.org/language/attributes.html#multiline-attributes).
```
<div
@ -17,7 +19,7 @@ The closing bracket should be on its own line. This allows attributes to be shuf
</div>
```
If the node doesn't have child notes, add the closing tag on the same line as the opening tag's closing bracket.
If the element doesn't have children, add the closing tag on the same line as the opening tag's closing bracket.
```
<div