Streaming changes according to Schwab_Trader_API_-_Streamer_Guide.pdf

[jacabreragt]

Field names were changed to match the Streamer Guide document. Timesales and News services were removed and Screener Service added. Implemented LOGOUT functionality and for each service ADD feature is implemented as well.

[jacabreragt]

Found out that ADD functions need fields to be sent in the request to the websocket so fixed that.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.55%. Comparing base (d14175a) to head (4c8c5b7).
Report is 7 commits behind head on main.

❗ Current head 4c8c5b7 differs from pull request most recent head 1ee2924

Please upload reports for the commit 1ee2924 to get more accurate results.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #127      +/-   ##
==========================================
- Coverage   98.87%   98.55%   -0.32%     
==========================================
  Files          18       18              
  Lines        2216     2214       -2     
  Branches      226      229       +3     
==========================================
- Hits         2191     2182       -9     
- Misses         17       21       +4     
- Partials        8       11       +3     

Flag	Coverage Δ
unittests	98.55% <100.00%> (-0.32%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jacabreragt]

Test cases related to the streaming module has been updated and added to reflect all the changes.

[alexgolec]

Initial round

[alexgolec]

Also it looks like you're causing a test coverage regression here: https://app.codecov.io/gh/alexgolec/schwab-py/pull/127?dropdown=coverage&src=pr&el=continue#8172eb34b156f7f11dfb8fa1008c98e5-L330

[alexgolec]

Thanks for this PR!

[mm0]

I believe this may have been done accidentally since other fields were modified where it does make sense to have the FUTURE prefix. Would it make more sense to keep this consistent with other contract/ticker types?

MARK_CHANGE_PERCENT instead of FUTURE_CHANGE_PERCENT