There is a Wolverine.Http.Marten and a Wolverine.Http.Polecat, and no Fisher equivalent. Noting it here rather than in the wolverine repo because it belongs to the Fisher-parity story; the code itself would live beside its two siblings in wolverine/src/Http/, so move it if that reads better.
Not a blocker: a CritterWatch console flavour compiled against Fisher builds and runs against plain WolverineFx.Http, because nothing in its endpoints reaches for the store-specific half. But the store-specific package is where the aggregate/document HTTP attributes live, so any Fisher application that wants those has nothing to reference, and "the three flavours' csproj files are the same file with one word changed" stops being true at this line.
Low priority — recording it so the parity list is complete.
There is a
Wolverine.Http.Martenand aWolverine.Http.Polecat, and no Fisher equivalent. Noting it here rather than in the wolverine repo because it belongs to the Fisher-parity story; the code itself would live beside its two siblings inwolverine/src/Http/, so move it if that reads better.Not a blocker: a CritterWatch console flavour compiled against Fisher builds and runs against plain
WolverineFx.Http, because nothing in its endpoints reaches for the store-specific half. But the store-specific package is where the aggregate/document HTTP attributes live, so any Fisher application that wants those has nothing to reference, and "the three flavours' csproj files are the same file with one word changed" stops being true at this line.Low priority — recording it so the parity list is complete.