ocket8888

Whoops, that PR referenced the wrong Issue. This is still open.

Looks like this only happens if it's literally a blank string. Something like `"This isn't a valid URL"` will properly return a 400-level error explaining that this isn't a URL.

Could be implemented as an [Angular Material "Tree"](https://material.angular.io/components/tree/overview)

Should we change the t3c tests to a matrix of the two OSes ? Right now this may fix it, but the default is to use Rocky 8 so the...

Well a matrix would be easiest, but if we shouldn't do that should it at least test them both sequentially?

You wouldn't, which is what I mean about matrix being the easiest way.

Sure, that's fine by me.

Note that this is a breaking API change; cannot be done in APIv3 (or probably v4 which is set to be released any day now).

> I'm also trying not to depend on the RPM build. It's just too many steps that are not needed. I been saying that for years, godspeed. We might use...

We're trying to favor query parameters over path parameters these days, so the API is designed with an eye toward that. The handler for `/foos?id={{ID}}` is in nearly all cases...