Tim Hansen

Thanks for the comments @Rugvip! ❤️ 1. The `NotificationContext` is a band-aid for not having a `notification-backend` and I expect it to be removed once the backend is place. The...

To @jhaals point, we had a discussion to think through what this would look like ideally in the end. There will likely be a general backend event stream, similar to...

Thanks @evankanderson, this is great to point out. CloudEvents were mentioned in the original issue, I'll take a closer look at this spec. We're re-evaluating the `Notification` type based on...

Recapping some thinking here as an update. We believe Backstage will eventually have an event/message bus available to backends, where things like catalog updates, build failures, audit logs of activity,...

@laceyallyn Very helpful, thank you! I haven't considered desktop notifications, but that could certainly add on top of this work once the frontend is receiving notifications. The second is perhaps...

@jrusso1020 No update at the moment as attention has been elsewhere, but I am striving to get back to this soon with some more experimentation.

@mtlewis and I spent a hot second looking at the [code in question](https://github.com/backstage/backstage/blob/9eccc589b7ebe3c2675a29f650bf2417d89d2573/packages/backend-common/src/reading/GithubUrlReader.ts#L267). As mentioned, there's not enough information in the URL to tell branch name versus path when the...

The above-linked lesscss-java [issue #41](https://github.com/marceloverdijk/lesscss-java/issues/41) has new comments indicating that a new release may come down the pipe after all.

The [documentation](http://docs.jboss.org/hibernate/search/3.3/reference/en-US/html_single/#d0e4578) seems to mention the capability: > If not specified otherwise, the query will be executed against all indexed entities, potentially returning all types of indexed classes. My particular...

Hmm, it's a good question. My initial thinking was something like: ``` groovy FullTextSession.search(DomainClass1, DomainClass2, DomainClass3).list { // query } ``` Granted, I was just evaluating the plugin for inclusion...