Figure out diagnostics abstraction for Update/Query.
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 379
- Avg merge
- 14m
- Merged PRs (30d)
- 8
Description
There are two identical traits that probably don't need to exist at all. Does it make sense to abstract out a supertype for Update and Query?
Contributor guide
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 locating the two identical diagnostics traits associated with Update and Query, then compare their APIs and usages. Determine whether a shared supertype is appropriate without changing the intended behavior, and verify that both Update and Query continue to expose the required diagnostics functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100