feat: expose parsing so that user can reuse it#39
feat: expose parsing so that user can reuse it#39qualiaenjoyer merged 3 commits intoqualiaenjoyer:mainfrom
Conversation
|
hmm, I think I'll accept this for now and decide later about your points. |
|
So, do you want to undraft it? |
…t cast in eip712 switched to mappings to help mypy
|
so I set it up to not log/print empty strings for now. also, lomond (the ws library) automatically pings and reconnects. |
|
I am a little bit confused about pyrefly, how do you run it? |
|
Why to use |
|
I do |
|
expose MarketEvents, UserEvents, LiveDataEvents? |
Yes |
Maybe check Also check this: |
iirc mypy treats it as read only or something. dict should work as well, but mypy probably interprets it as mutable |
I didn't know, then it's fine |
also use .venv inside project, config and version look identical |
I frankly have no idea, you can merge |
Fixes: #33
However I need to discuss 2 questions:
process_event(parse_market_event(cast("Text", event)))? In this case it makes callback easier to use, but it erases some error information. We can also generalize it to returnTextonly in the case when parsing was unsuccessful, likedef cb(event: MarketEvents | Text).