Eric Peterson

Hey @pedronastasi! Thanks for starting discussion on this. Definitely understand the desire to have a bit of an escape hatch to be able to work around limitations of the interface,...

Thanks for the patience on this, @pedronastasi! How about we focus this issue on just support for `aggregations`, and we can keep the issue linked by @camilaibs as a relation?...

Hey again @pedronastasi! Thanks for illustrating in more depth. Wwhat a great user experience! This conversation happened to align with an architecture ritual we have internally, and we were able...

That sounds reasonable to me! A test for the change would also be great. ...And a descriptive changeset as well. (You can take a look at other recently merged PRs...

Ah, yeah! We're all good here, I think, as this PR was merged in about a week ago: https://github.com/backstage/backstage/pull/13890 Should be available to try out as of `@backstage/plugin-search-backend` version `1.1.0-next.1`...

Handing this PR off to you, @realandersn

Hey there! In order to use TechDocs successfully with the permissions framework, you will need to include some extra code in your backend that sets the auth token on a...

As far as I can see, this is documented most directly here (https://backstage.io/docs/permissions/getting-started#optionally-add-cookie-based-authentication), which provides some better context. You'll see it still links out to the tutorial I linked to...

Found myself here as a result of running Puppeteer Cluster in resource-constrained PaaS/IaaS environments and running into this error intermittently. I like the idea of a different error type from...

This proposal is kind of close: #67 ...But it's more about the next layer down than the top-level navigation. I'm not aware of a way to auto-generate an entire navigation...