-
Notifications
You must be signed in to change notification settings - Fork 1
[ARCHIVED] 2020 Roadmap
¡Támb! edited this page May 7, 2020
·
1 revision
- This way you can use whatever you like to represent event-handling, props, etc. This should remove some cases where the syntax of Domponent may collide with a template language.
- As it stands, the library does not have enough integration tests. They're a pain to write, but I'll do them.
- Mustache
- ASP
- Twig
- This could organize the components better and automate garbage collection
maybe through a directive likedata-attr-bind='{"class": "|state.field:classname|"}'
- Perhaps create a
watch
function that does apre
andpost
function perprop
orstate
field. ✔️ - A watch would fire for that individual field. So you could keep your rerendering logic around that field more organized as opposed to everything in
stateDidUpdate
✔️ Alternatively, I could create auseHook
module to bring in, in a similar way to React
watch(){
return {
count: {
pre(){
// my update
},
post(){
// my update
}
}
}
}
I could also addcomputed
to it. Like in Vue-
NEED TO ADD FOR
props
AS WELL ✔️
-
data-if
would remove sections of the component from the DOM depending on component state/props -
data-show
anddata-hide
would add a conditional class to the DOM element depending on state/props
- potentially add
data-html
tag to allowprops
andstate
to render HTML. - potentially add option binding value
data-bind="state:Counter.count,html"
- potentially allow state and props fields to be flagged in constructor
- WHAT IS THE MOST SECURE WAY TO DO THIS?
3rd argument to
setState
?
this.setState({}, cb, true|[])
array is string of field names to render innerHTML
for during that particular setState
. If set to true
all fields will set innerHTML
Add additional exponent method to parse a section of html and create a new component and method to bind more to current component. This will aid in adding html dynamically that needs domponent functionality
-
addHTML
andremoveHTML
could be methods to which accept acontainer
element and wire up all the event listeners and new components within that region. - alter current component utilities to allow for a dynamic root element. This should promote reuse of utilities