Use well-typed errors
@JarvisCraft is already working on this.
Since Mar 16, 2025.
Assessment
This issue has not been assessed yet.
Description
Problem
Currently, enum Error is just a bunch of typed Strings which has the cons of:
- Being hard to use it in granular manner;
- Requiring allocations per each string which may never be used.
There also is a problem of not using the std::error::Error::source() infra.
Solution
Replace this with a well-typed error using thiserror for declarative definition.
PS: self-assigning the issue as I am already working on it.
- Dominant language
- Rust
- Stars
- 275
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
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.
More from ozontech/pg_doorman
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ozontech/pg_doorman#276 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ozontech/pg_doorman#274 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
ozontech/pg_doorman#107 · 1 comment ·
All issues in ozontech/pg_doorman
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100