Sam

I'm aware I could do that, but it would mean that I'm constantly tracking your work. Instead of having it as part of the core project where any breaking change...

> One more vote for Svelte; I don't want to waste cycles researching (and supporting) a hack via importing another framework You refer to the knockout framework in that case...

> BTW: I think it would better to ensure that we search for `://` only before `?` instead of relying on `parse_url()`) and these functions could be called hundreds of...

@ggh2e3 can you give some example of inconsistencies in the old code? Because while they might be considered bugs they could also be behavior people depend on.

I don't see changes to the Base URL class in this PR though.. am I missing something? (Sorry on mobile so not ideal for browsing gh)

Great, will see if I do :+1:

The goal is to be able to identify errors based on the exception class only. So as a consumer of the library I'd want to do something like this: ```php...

Regardless of the type of record (SRV / A) could / should this not be a separate service that you deploy on the cluster? All it has to do is...

> Relations may use different repository/connection. They won't use a different repository; think of the repository as a factory or service locator for just DB connections. You would have 1...

(I'm making this up as I go) The repository could be configured in the DI container like this: ```php [ 'db1' => [normal db config], 'db2' => [normal db config],...