Marshall Cottrell

I had started to spec out an API for this in https://github.com/neumino/rethinkdbdash/issues/334#issuecomment-293423825. That's probably a good starting point if anyone wants to submit a formal proposal.

@rikatz thanks for the explanation, makes total sense! I didn't realize just how recently the `TTLAfterFinished` feature gate was promoted to beta. > ... anyone deploying ingress nginx in versions...

As a side-note, it would also be nice if the `name` parameter to the various `Param` decorators was optional and defaulted to the property name (both in the `class` example...

@19majkel94 yea it's not so much about syntax or readability, though I think there is some benefit there. As you mentioned it also plays nicely into `class-validator` and being able...

> The same problem would be with `@Req` and `@Res` - on the client side you would have to pass dummy object as any? It makes no sense. @19majkel94 that's...

@pleerock in that case you would no longer be able to use `@Inject()` and other DI utilities. You'd be responsible for resolving all dependencies of the controller yourself, correct?

It might be nicer if we could introduce a proper keyword here and make it behave more like `range` or `with`: ```hbs {{ try $value, $err := "hello = \"Hello...

@bep ah, I assumed there would be some API to add keywords/rewrites similar to how you can expose custom functions. Given that's not the case, perhaps we can avoid introducing...

@bep that's fair but use cases outside of `resources.Get/GetRemote` and/or `unmarshal` seem sparse. HTTP and parser errors are about the only thing you'd ever care to print/introspect in a template....

@ThomasBurleson can we reopen this issue for some further discussion? I was about to start working on a PR for introducing `md-button-group` as a first-class component, but quickly realized there's...