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
exportlettotal// total += 1// require compiler// (maybe compile to class// with @bind accessor// for the sake of performance// 😂)exportconsttotal={}// total.value += 1// works without compiler but weird
The reason I'm interested in named export is because of handleEvent() pattern in class1
Seems the only compromise for avoiding data-binding footgun is to only allow named exports for handling ref Element #9. Basically named export must be a function or class. With this limitation, top-level attribute is not necessary.
I think I will go with ! prefix and only limit named/top-level export function for ref element, event handler, and setter/getter (choose one). Would be nice if I can support this context too.
DrSensor
changed the title
Support named/top-level export
Support named export (top-level binding)
Mar 6, 2023
The reason I'm interested in named export is because of
handleEvent()
pattern inclass
1use module in other area or projects
Footnotes
DOM handleEvent: a cross-platform standard since year 2000 ↩
The text was updated successfully, but these errors were encountered: