Justin Fagnani

We're addressing this in Lit 3.0 with the new standard decorator implementations. Standard decorators get access to the initial value and can skip reflection for those values. This is being...

Update: we're going to address this in a follow up to 3.0. We were initially going to solve this with the standard decorators implementations which can differentiate initial values. Instead...

But not metadata, which we need for attribute conversion. I'm hoping that's settled by TypeScript 5.1

@tronicboy1 The problem isn't accessing the instance in the decorator implementation, the problem is that the `@eventOptions` decorator reuses all the options given on every host instance, but with a...

I think that one way to think about Task's render() helper and this problem is that render() is there for a relatively common case where task states are mutually exclusive,...

Since the task value is now preserved between runs, and there's a workaround of not using render (or accessing the task's value in render/pending). I'm going to close this as...

@ChadKillingsworth talking with more SSR users recently makes me think we'll need to support this - it's just a question of when we can get to it. Technically what we...

I would be open to a PR for this. Last-in wins sounds fine, considering that should be the current behavior with collisions just from JS object semantics. edit to add:...

Thanks for those steps! I did get things working in a pretty acceptable way, but I hit some other speed bumps that might be good to document: - I use...

I definitely don't have time right now, so that'd be great @43081j ! I guess it'd be nice to file issues/PRs on Webpack to export the type interfaces needed here.