You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, there is an assortment of code of different ages for different parts of the system for managing queries. We rely on multiple existing macro based libraries to extend ecto.
Before I took a break from bonfire for a few months, i did much of the work on a new library called queery. Here is a snapshot of some user-level documentation I wrote for it: gist.
I propose to finish up this work now while I have to update some of this old code in the contexts anyway
The text was updated successfully, but these errors were encountered:
Rather too much learning about how ecto works later, i've concluded that while it's possible, it wouldn't be advisable since we'd have to rely on ecto internals or do incredibly bad things to make it work and the last thing i want to do is rewrite tons of code because ecto changes.
At the moment, there is an assortment of code of different ages for different parts of the system for managing queries. We rely on multiple existing macro based libraries to extend ecto.
Before I took a break from bonfire for a few months, i did much of the work on a new library called
queery
. Here is a snapshot of some user-level documentation I wrote for it: gist.I propose to finish up this work now while I have to update some of this old code in the contexts anyway
The text was updated successfully, but these errors were encountered: