issues
search
jxnblk
/
macro-components
Create flexible layout and composite UI components without the need to define arbitrary custom props
MIT License
484
stars
24
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Failed prop type: Invalid child component `[object Object]`. Must be one of: Cover, Body, Footer
#10
okonet
opened
5 years ago
2
Next API
#9
jxnblk
closed
6 years ago
0
RFC: Explicit API
#8
gaearon
closed
6 years ago
4
Add support for using components without a displayName
#7
jxnblk
closed
6 years ago
0
Add optional childTypes argument
#6
jxnblk
closed
6 years ago
0
Remove component name check
#5
jxnblk
closed
6 years ago
0
Add a section on drawbacks/alternatives
#4
gaearon
closed
6 years ago
1
Relying on function.name is brittle
#3
gaearon
opened
6 years ago
23
Added module entry point (+ refactored build setup)
#2
Andarist
opened
6 years ago
0
Functional API
#1
jxnblk
closed
6 years ago
0