I think I understand but it's the attributes API that's confusing. I expected to use attrs -- and they're the thing that's string based.
-
-
Replying to @pfrazee
You don't need to implement attribute support of you don't want to.
1 reply 0 retweets 1 like -
Replying to @slightlylate
Here's the problem. yo`<my-component thing=${value}></my-component>` is the pattern I expect. Yo-yo will do setAttribute('thing', value)
1 reply 0 retweets 2 likes -
Replying to @pfrazee @slightlylate
Which is a common-sense choice prior to WCs, but now I want to do what I do with react, eg: <my-component thing=${arrayOfValues}>
1 reply 0 retweets 1 like -
Replying to @pfrazee @slightlylate
So we'll need to modify yo-yo to do myComponentInst.thing = arrayOfValues instead... I guess under some heuristic for what should be a prop
4 replies 0 retweets 1 like -
Replying to @pfrazee @slightlylate
cc
@mikeal this is what I was talking about the other day2 replies 0 retweets 0 likes -
Replying to @pfrazee @slightlylate
so, i dont think the optimal way to present functionality is to own the entire element creation pipeline.
1 reply 0 retweets 3 likes -
this immediately puts you in the framework world because in order to access you work is to call it in a specific way.
1 reply 0 retweets 4 likes -
once you give up on that and say “it’s just an element,” there are many ways to create an element.
2 replies 0 retweets 3 likes -
mmmm, but they are limited. You can't `const elem = new MyElement()` if you are extending HTMLElement.
2 replies 0 retweets 0 likes
Of course you can. That was half the point of the exercise = )
-
-
Replying to @slightlylate @bradleymeck and1 reply 0 retweets 1 like
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.