Eunan Camilleri

@ramswaroop Any update on the progress of this? It would be excellent to have the ability to include this field value as part of the attachments as side by side...

There's a code example [here](https://api.slack.com/docs/messages/builder?msg=%7B%22attachments%22%3A%5B%7B%22fallback%22%3A%22ReferenceError%20-%20UI%20is%20not%20defined%3A%20https%3A%2F%2Fhoneybadger.io%2Fpath%2Fto%2Fevent%2F%22%2C%22text%22%3A%22%3Chttps%3A%2F%2Fhoneybadger.io%2Fpath%2Fto%2Fevent%2F%7CReferenceError%3E%20-%20UI%20is%20not%20defined%22%2C%22fields%22%3A%5B%7B%22title%22%3A%22Project%22%2C%22value%22%3A%22Awesome%20Project%22%2C%22short%22%3Atrue%7D%2C%7B%22title%22%3A%22Environment%22%2C%22value%22%3A%22production%22%2C%22short%22%3Atrue%7D%5D%2C%22color%22%3A%22%23F35A00%22%7D%5D%7D) - but the field documentation can also be found [here](https://api.slack.com/docs/message-attachments#fields)

Uncertain if this is relevant but I'm running into this issue using a Micro-frontend architecture. The problem-space is that these are distinctly two different applications with separated sources and write...

Thanks @silesky To elaborate, the container application is legacy and uses a snippet. The child container uses the direct npm dependency and `AnalyticsBrowser` class to instantiate analytics. If I migrated...

Yep, I found this too, it was very buried but it **is** documented in the code. This appeared to work fine, and instead of altering the parent container for a...