Skip to content

Core module split - #26

Open
juicycleff wants to merge 2 commits into
mainfrom
core-module-split
Open

Core module split#26
juicycleff wants to merge 2 commits into
mainfrom
core-module-split

Conversation

@juicycleff

Copy link
Copy Markdown
Contributor

No description provided.

EngineOption named *fabriq.Fabriq to look the facade up in the container.
That one type parameter pulled in fabriq's composition root and every
adapter it wires, so a package whose entire use of fabriq is f.Vector()
was linking ClickHouse, Elasticsearch, pgx, go-redis and Trove.

Injecting core/query.Fabric instead takes the build graph from 1418
packages to 254 and clears all of those drivers out. go.sum loses 92
lines with it.

It also means an engine reached over the wire drops straight in. A
deployment registers *remote.Fabric under the same port key and nothing
here changes.

The replace directive is local dev. Repin to a released fabriq and drop
it before this merges.
Weave uses the query port and a handful of fakes. Requiring the root
module pulled fabriq's entire go.mod into resolution, so every driver it
names sat in our go.sum regardless.

The replace is local development only. Repin to a tagged fabriq/core and
drop it before this merges.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant