Handling Case-Insensitive Branded Strings in fp-ts to Effect Migration
Is there a sensible pattern for having a branded string that's also considered case-insensitive? An example would be a UUID: currently the type from
@effect/schema is case sensitive, i.e. https://effect.website/play#740ec405631e should pass. I have a few of these types I'm looking to handle in an fp-ts to Effect migration (another being DOI).
