crossbario / crossbario/autobahn-python
Component-API cleanups
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 768
- PR merge metrics
- No merged PRs in 30d
Description
It might be nicer and more natural to run any "main" procedure specified in a Component on the "ready" signal (currently it runs at "on_join" time). This would allow other "setup-style" things to run completely in "on_join" before running the "main" (if any).
Another thing that might be less surprising is to make "fatal errors" configurable, with "nothing" being the default. A "fatal error" is defined as anything that would fail a transport and thus cause us to give up on trying that transport again.
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 tracing the Component lifecycle around the on_join and ready signals, then inspect how transport-failing errors are classified. Done means main procedures run on ready after setup work in on_join, and fatal-error handling is configurable with nothing as the default; add coverage for both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100