FiloSottile / FiloSottile/sunlight

Reconsider crawshaw.io/sqlite dependency?

Open
#71 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
307
Forks
29
PR merge metrics
No merged PRs in 30d

Description

Hi! In https://github.com/FiloSottile/torchwood/issues/27 you replaced crawshaw.io/sqlite with zombiezen.com/go/sqlite however sunlight still uses crawshaw.io/sqlite, which leads to two sqlite mappings since sunlight depends on torchwood. Is zombiezen.com/go/sqlite appropriate for sunlight too? Or are there other considerations?

Thanks,
Simon

Contributor guide

Open the contributing guide

Research direction

Start by tracing sunlight's crawshaw.io/sqlite usage and its dependency on torchwood, then compare that with torchwood issue #27's switch to zombiezen.com/go/sqlite. Determine whether sunlight can use the same SQLite mapping without other considerations; done means the dependency choice is resolved and duplicate SQLite mappings are addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, sqlite
Domain
backend, databases
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.