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
createComponent -> setupComponent -> fallthroughAttrs -> setDynamicProps results pulling all the props handling code
we need to rethink how fallthrough attributes are handled, maybe by moving fallthrough attributes application code to be generated in the parent component where the child is consumed.
setup() returning object is only needed in __DEV__ (hmr)
setDOMProp
on static tag + keyperf(runtime-vapor): optimize
setDOMProp
on static tag + key #294recordPropMetadata
#297runtime/compiler-vapor
andruntime/compiler-dom
compiler-dom
andruntime-dom
to peer dep forcompiler-vapor
andruntime-vapor
(see refactor(runtime-vapor):setStyle
reuse from runtime-dom #295 (comment))compiler-vapor
should reusehtmlNesting
logic fromcompiler-dom
refactor(compiler-dom/vapor): reuse html nesting from compiler-dom #298
getSequence
from corecreateVaporApp
should reuse logic from createApp inruntime-core
setStyle
reuse from runtime-dom #295on/delegate
is pulling in all the modifier coderefactor(compile-vapor): wrap the event handler with
withModifiers
orwithKeys
#300createComponent
->setupComponent
->fallthroughAttrs
->setDynamicProps
results pulling all the props handling codesetup()
returning object is only needed in__DEV__
(hmr)setup()
returning object is only needed in __DEV__ (HMR) #296renderEffect
The text was updated successfully, but these errors were encountered: