fuelen / fuelen/ecto_dev_logger
Thank you — and reusable SQL formatting
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 181
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
I’ve implemented something like the formatter bits of ecto_dev_logger in the past, but your approach here was very clean and helped me with an investigation that I was looking for.
I have suggested to the Ecto team that Ecto (SQL) probably should have formatter functions and callbacks to the adapters for the differences as you have implemented, and that your formatter code might be a really good start for this.
If that's rejected, can I suggest extracting the SQL formatter code from ecto_dev_logger into a separate repository/package so that it is usable by others? We’ve written an inspect_sql function that has similar formatting functionality (focused only on PostgreSQL for now), but I think that if the Ecto team doesn’t have any interest in a formatter by default, having a community package focused on formatting would be the next best option.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the formatter code in ecto_dev_logger and the related inspect_sql functionality described in the issue. Check the linked Ecto discussion before deciding whether this belongs in Ecto or a separate package. Done is not defined: the issue leaves the destination, scope, and acceptance criteria unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100