Ernest Landrito

I took a stab at seeing if we could declare the events as a Type parameter to the `LitElement` class such that: 1. If you don't parameterize on any `Event`...

**_If_** we could get the `Event` and all `extends Event` types to follow the update above, the interface for this becomes much simpler: ```ts // No more need of this...

Thanks for the detailed and thoughtful response @ChristianUlbrich! > * messing around with `LitElement` directly; if going that route, I think sth. along a [class-based mixin expression](https://justinfagnani.com/2015/12/21/real-mixins-with-javascript-classes/) (btw. @justinfagnani nice...

To tie this back to the original proposal: > ```ts > class MyElement extends LitElement { > @event() onFoo!: (e: FooEvent) => any) | null; > > render() { >...

This is a good idea. I think adding a method to the the testing service would be a good way to do this.

I'd also like to make sure that there is no overlap in what can be represented in the annotations and the configuration. Currently `scopes`, `default_host`, and `port` can be represented...

I think it's fine to leave em in until we have them more API's. Internally we are working out a strategy for getting those annotations into all the APIs in...

The intended input of any gapic-generator-{language} in github.com/googleapis are is protos that use the annotations [api-common-protos/google/api](https://github.com/googleapis/api-common-protos/tree/master/google/api). This normalizes the interface across all the generators so that users that buy into...