Closed lue-bird closed 2 years ago
My version is fully backwards compatible with bChiquet's... so there shouldn't be anything that prevents people from trying out my version which just has more accessors built in.
The named
vs unnamed
is mostly irrelevant until I figure out the rest of this Form abstraction I've been doing all of this to support.
But the named and unnamed accessor types are not compatible, right? → The current, named versions are only compatible with your package
But the named and unnamed accessor types are not compatible, right?
They ARE compatible. This is what I've been trying to say. I explicitly made them all backwards compatible.
Nah, we're still talking past each other.
Defining the variant prisms by Accessors.makeOneToN_
which is what you PRed and what I'd like to keep as the default is only available in your package, not in bChiquets.
Only the unnamed version is working with either package → this issue will keep me reminded to add such an unnamed version.
Ah yup, got it. Correct. I'm using the "extended" version for generating lenses with unique names but my version of the package keeps the same module heirarchy as bChiquets so the generator for the unnamed version should still work for both packages.
👌
Added VariantPrism.GenerateUsed.accessorsBChiquet
The default
VariantPrismGenerator
namedaccessors
generates namedAccessors
by @erlandsona. The unnamed version is for users ofbChiquet/elm-accessors
or those should help transition to namederlandsona/elm-accessors
.