Parse proto for inmemorysubscriber
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
Research direction
Read inmemorysubscriber.py, especially lines 106-108, and inspect the Protofile for the subscription definitions. Confirm that subscribe, unsubscribe, and notification_uri are obtained from the Protofile rather than hardcoded, then verify the subscriber uses those parsed values.
Written by the indexing model from the issue text.
Description
inmemorysubscriber.py, lines 106-108 currently hardcode the values for subscribe, unsubscribe, and notification_uri. Those should be parsed from the Protofile for subscription.
- Dominant language
- Python
- Stars
- 3
- Forks
- 13
- Avg merge
- 5h 28m
- Merged PRs (30d)
- 1
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 eclipse-uprotocol/up-python
-
help wanted
Difficulty 5/5 Over a week Newbie friendliness 20/100
eclipse-uprotocol/up-python#64 · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Add OFT tags Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in eclipse-uprotocol/up-python
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·