Good day alchemists,
Have you been writing Ecto schemas on the Web layer only to find it all a tad tedious?
Writing one for each controller action can get tiring real fast. Not writing them makes you feel insecure about sending those params to the data layer.
Fret not, I’ve released a small utility library to help with this, and I think you’re going to like it.
It is used in production for almost two years at Fave, and I’ve released some improvements to the library.
Check it out here:
I’m looking to extend the v2 with built-in features provided by Ecto like:
I have some ideas on parsing the AST to OpenAPI specification, but I could use some help and guide.