Common function `_reject_invalid_json` in both Synapse and Sygnal
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by locating _reject_invalid_json in Synapse and Sygnal and comparing its implementations and callers. Determine how the common behavior could be shared, then verify that existing behavior remains covered by the relevant tests; done means the duplicated function is no longer maintained separately.
Written by the indexing model from the issue text.
Description
Noting common function _reject_invalid_json in both synapse and sygnal
Originally posted by @H-Shay in https://github.com/matrix-org/matrix-python-common/issues/1#issuecomment-966597137
- Dominant language
- Python
- Stars
- 4
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
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.
More from matrix-org/matrix-python-common
-
Difficulty 3/5 Half a day Newbie friendliness 35/100
matrix-org/matrix-python-common#14 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
matrix-org/matrix-python-common#2 · 4 comments ·
All issues in matrix-org/matrix-python-common
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100