issues
search
voorhoede
/
riotjs-style-guide
Opinionated RiotJS Style Guide for teams.
Creative Commons Zero v1.0 Universal
287
stars
22
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add "back to table of contents link" to contribution format
#15
jbmoelker
closed
8 years ago
0
"Keep tag options primitive" rule
#14
jbmoelker
closed
8 years ago
0
Link "LIFT principle" in "1 module = 1 directory" rule?
#13
jbmoelker
closed
8 years ago
2
"module based development" extension: tag file <100 LOC
#12
jbmoelker
closed
8 years ago
0
"Avoid `tag.parent`" rule
#11
jbmoelker
closed
8 years ago
0
"Tag name as style scope" rule
#10
jbmoelker
closed
8 years ago
0
"Put styles in external files" rule
#9
jbmoelker
closed
8 years ago
3
"Keep tag expressions simple" rule
#8
jbmoelker
closed
8 years ago
1
"Module tag names" rule refinement
#7
jbmoelker
closed
8 years ago
0
"use `*.tag.html` extension" rule
#6
jbmoelker
closed
8 years ago
5
"use `<script>` inside tag" rule
#5
jbmoelker
closed
8 years ago
3
"1 module = 1 directory" rule
#4
jbmoelker
closed
8 years ago
5
Pull Request template
#3
jbmoelker
closed
8 years ago
0
Component / Tag names
#2
petergoes
closed
8 years ago
1
Module based development
#1
jbmoelker
closed
8 years ago
5
Previous