Aramis Sennyey
Aramis Sennyey
I wonder if a combination of metadata on annotations`*` and decoupling the API spec from the API entity would solve this nicely. You could put version on your provides/consumes relationship...
@acunniffe Thanks! All of them, here's the test, https://github.com/backstage/backstage/blob/542d19100dc054168561ca704ce287018932f5ea/plugins/search-backend/src/service/router.test.ts#L82, no query parameters defined at all.
@acunniffe 🤦 that's my bad, I should have looked through the rest of the tests. Using `it.only` works. I think this is an issue with my spec, https://github.com/backstage/backstage/blob/542d19100dc054168561ca704ce287018932f5ea/plugins/search-backend/src/service/router.test.ts#L217 looks really...
@acunniffe A little more looking later, 1. The way the Backstage library is creating query parameters and denoting them is _really_ non-standard, using `a[0]=x&a[1]=y`, which is supported by the `qs`...
Should also add that this isn't super time sensitive, I'm happy to keep using 0.50.10 for the time being 😁
@acunniffe Ah, that's a huge step forward for the tool 😁 ! Hadn't realized that was what changed 🤦 . For sure, take your time, I'm happy with the current...
@freben Appreciate you reading through it! I'm with you. Looking back at the text, most of the use of `annotations` was my brain mixing up "annotations" and "relations". I thought...
@Rugvip Updated to a separate `CatalogModelExtensionPoint` with `addPolicies` and `replacePolicies`. Are there any other chunks we may want to include in this work?
@freben Appreciate the in depth comment! Definitely agree, I've updated this PR to make `addPolicies` deprecated on release, added a new `policyToProcessorTransformer`, and added support for field validators on the...