Description
As a user of the figlet library I would like to use the Validated applicative to handle figlet errors or, at worse, add support for my own effect.
I would like figlet to have a package that wraps results in Validated and a package that directly exposes the generic effect F[_].
Implementation
Add two new packages in the figlet4s-effects project, one for Validated and one for generic and use the existing packages as starting point to implement this feature.
On a different thought this might require a rethink of the structure of the packages because, like it is now, when importing the effects library a whole lot of unwanted dependencies can be added. I.e. if I want to use support for Either I'm forced to depend on Cats. Do not proceed before taking a decision with this.
Notes
For small, self-contained library like figlet4s I believe in the "battery included" approach and easy integration. For this reason I don't want users to fiddle with conversions to and from effects that they are not currently using in their library and this is why I want to add support for the most common and reasonable effect in the Scala ecosystem.
Description
As a user of the figlet library I would like to use the
Validatedapplicative to handle figlet errors or, at worse, add support for my own effect.I would like figlet to have a package that wraps results in
Validatedand a package that directly exposes the generic effectF[_].Implementation
Add two new packages in the
figlet4s-effectsproject, one forValidatedand one for generic and use the existing packages as starting point to implement this feature.On a different thought this might require a rethink of the structure of the packages because, like it is now, when importing the effects library a whole lot of unwanted dependencies can be added. I.e. if I want to use support for Either I'm forced to depend on Cats. Do not proceed before taking a decision with this.
Notes
For small, self-contained library like figlet4s I believe in the "battery included" approach and easy integration. For this reason I don't want users to fiddle with conversions to and from effects that they are not currently using in their library and this is why I want to add support for the most common and reasonable effect in the Scala ecosystem.