Re:The Svelte Compiler Handbook
by chrismorgan on Sunday April 05, 2020 @11:41AM
(#22786183)
What you’ve written there couldn’t possibly be reactive without compilation or wrapping it in a function. Is there something else wrapping it (a function), or is it being compiled into a different form? If it’s being compiled (so that the code means something other than it seems to), then I see no particular advantage to using TypeScript syntax, given it’s more verbose than need be.
For reference, in Svelte that’d be something like this, which is shorter and more obvious:
<div class="bold smart" id="abc" bla={true} on:click={() => { console.log("Clicked") }>
hello, {store.user.name}
</div>Yes, that's currently what I'm experimenting with.
This is very early stages and completely experimental.
The idea I'm experimenting is to compile typescript to another form, I completely see your point about too verbose though, but I'm also toying around with jsx.
Basically what I'm trying to do is a svelte where instead of this:
{#each cats as { id, name }, i}
<li>
<a target="_blank" href="https://www.youtube.com/watch?v={id}">
{i + 1}: {name}
</a>
</li>
{/each}
You have have the native JavaScript map functions and so on.Again, this is completely in the early stages and just playing around until something feels right.
Any recommendations appreciated.
Is there any framework that explicitly allows me to set properties instead of just attributes? It doesn't play nice with web components when the object you passed in comes out as a string "[object Object]".
What do you mean? how would it look?
Using 'evts' instead of events is a good way to get people to make mistakes
Thanks for the feedback :)
Re:The Svelte Compiler Handbook
by bufferoverflow on Sunday April 05, 2020 @10:41AM
(#22785795)
That is awfully verbose.
I'll hopefully add jsx eventually that will help with the visual aspect of the verbosity.
What's wrong with being verbose?
Re:The Svelte Compiler Handbook
by bufferoverflow on Monday April 06, 2020 @07:48AM
(#22792849)
You need to write more, you need to read more, and whoever maintains your code will need to read more. More chances for typos. That means more time wasted for everyone.
Why do you think we have async/await now instead of manually typing out all the promise syntaxic mess every time?
I'm basically trying to do a superset of typescript where you create elements so:
And store store.user.name is "magically" reactive.Was that what you meant?