hehonghui / hehonghui/AndroidEventBus
1.0.5貌似ticky事件被消耗以后并没有被清除掉
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.6k
- Forks
- 390
- PR merge metrics
- No merged PRs in 30d
Description
我自己的解决方案（仅供参考）：修改源码，在DefaultEventHandler的handlerEvent方法中添加了一句话
EventBus.getDefault().removeStickyEvent(event.getClass(), subscription.eventType.tag);
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.
Research direction
Start in DefaultEventHandler.handlerEvent and inspect how the consumed sticky event is handled. The issue proposes calling EventBus.getDefault().removeStickyEvent with the event class and subscription tag; verify that the sticky event is removed after consumption and confirm the behavior with a focused reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100