External datetime package synergy
Nobody has claimed this yet.
- Dominant language
- Gleam
- Stars
- 264
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Is there anything I can do to [Tempo](https://hexdocs.pm/gtempo/index.html) to make using it with Pog more ergonomic? Would adding `to_pog` and `from_pog` functions to the Tempo library make sense? Should `to_tuple` and `from_tuple` functions be added for the date / time functions in Pog to make them easily usable with any other package? Should we just leave it alone and let users write their own middleware? I am open to any ideas. [Relevant issue](https://github.com/jrstrunk/tempo/issues/4).
I honestly use SQLite mostly so Postgres date stuff is not something I am experienced with, but I know it is popular.
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 reading Pog's date/time functions and the linked Tempo issue to understand the existing integration concerns. Compare the proposed Tempo to_pog/from_pog functions with Pog's to_tuple/from_tuple alternatives; done requires an agreed API and implementation scope rather than an open-ended list of ideas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100