Repository navigation
Patch Changes
-
#4741
74a44adThanks @LuLaValva! - Explain how to act on<let>writes when it is given an event handler such asonChange, and how to bind with a fallback when:=is given??or||. -
#4753
b2b661eThanks @DylanPiercey! - Astyleproperty may now appear only once across astylevalue. A repeat the compiler can see, such asstyle=["color:blue", { color: tint }]orstyle=[{ color: a }, { color: b }], is a compile error, and one known only while rendering, such as an imported part that also setscolor, throws in development. Before, the server wrote every declaration so the later one won, while the client could keep one in the template and update the other alone, so the two disagreed. Give each property one source, such asstyle={ color: tint ?? "blue" }.In exchange more
stylevalues update one property at a time: an imported part such asstyle=[base, { color: tint }]stays in the template, and onlycolorupdates whentintchanges. -
#4752
ab416adThanks @DylanPiercey! - Fix values lost on resume when a template or<define>renders itself, or reads the tag variables of several calls to one<define>: content an outer instance passes down reads the outer instance's values, and a tag variable no longer takes another instance's state for its own. -
#4750
0eec052Thanks @DylanPiercey! - Fix dynamic tag names typed wrongly from a named import of a template or a number beside a template. A tag name that is a hoisted<const>whose value is certainly not a function (<${Tag}/>above<const/Tag=Child/>) no longer compiles: it read the value from outside the tag that declares it, so it rendered even where that tag did not. A native tag's event or change handler that is certainly a truthy value other than a function (onClick=(input.x ? "a" : "b"),onClick=("alert" + input.y), or a<const>holding a string) no longer compiles. -
Updated dependencies [
7257bdc,7257bdc,7c37c20]:- @marko/compiler@5.43.6