Jonathan K. Stevens

@stephenh is there a special option I need to provide or is this a bug?

@stephenh it seems to be that using these wrapper types works when they are embedded in a message, but fail the typescript compiler when they are used as the RPC...

@boukeversteegh it seems like you've done work with the wrapper types. Do you have any ideas here?

What's the hold up on this PR? This is the one thing holding us up from implementing this library.

I think you're referring to the [notification template data structure](https://prometheus.io/docs/alerting/latest/notifications/#data-structures). That is different from the [alert field templates](https://prometheus.io/docs/prometheus/latest/configuration/template_reference/#alert-field-templates). Notification templates are applied as an alert manager config and could look...

Created a [PR](https://github.com/prometheus/alertmanager/pull/2919) to add support for accessing the [template.Data](https://github.com/prometheus/alertmanager/blob/23f961ec6a9c8a15bf99c83815d35e13d66a4d5d/template/template.go#L236) in prometheus alert templates.

Anything I'm missing here to get some traction on this? It would be really helpful to customize alert notifications if that data structure was exposed. Instead of altering that data...

Any status on this? We're still getting this error.

Has there been anymore movement on this? The issue(generating X* for optional field) is still preventing us from using this.

@awanlin that makes sense for the javascript library, but not for the "pre" elements with mermaid classes. Why would it sanitize native `` tags? It's also writing it as if...