I just released my first hex package, EctoFlex.
make querying schemas extremely fast and easy (in terms of development time). No need to write your own queries to fetch simple data.
I used to write my general “querying” module for every new project that uses ecto and then slowly add some specialized queries as I go on. It used to take from a few hours to a few days to get everything together. It wasn’t practical. I felt like I was repeating myself unnecessarily and most of the code was filled with hardcoded values that prevented me from using it easily in other projects. Hence,
ecto_flex was born.
What It’s NOT
ecto_flex is not meant to replace complex queries. For example, it doesn’t support preloads (yet). It doesn’t support aggregate functions too. I’m not sure if this will be added in the future or not.
Why is it called “EctoFlex”?
It’s supposed to mean “Ecto Flexible” or “flexible ecto” in plain English. It helps you write flexible queries extremely easily. At least that’s what I hope. The docs for hex recommend to prefix the package name with the package that it depends on, so
ecto_flex it is.
It’s obviously in a very early stage and it’s not recommended for production use.
My plan is to keep enhancing it and adding features until I feel comfortable releasing a 1.0.
Criticism and feedback are welcome.
PRs are also welcome.