v2.0.1 #157
mattsta
announced in
Announcements
v2.0.1
#157
Replies: 1 comment
-
Hey Matt - just wanted to thank you and Gonzo for all the time and effort you guys have put into maintaining & improving this repo. I hope to be able to continue supporting you financially, though you deserve much more than my meagre contributions... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First "proper release" in almost a year. Includes many bug fixes and new usability helpers.
Thanks to contributors, people who continue to provide ongoing donations, and thanks to @gnzsnz for his continual consistent rapid replies and feedback on support/development issues.
Changes
Commit Changelog: v1.0.3...v2.0.1
Code diff: v1.0.3...v2.0.1
Docs Changelog: https://ib-api-reloaded.github.io/ib_async/changelog.html#ib-async-changelog
New Feature Highlights
One large usability improvement in this release is now you can specify your own custom values for "no price" or "no size" or "no value available" situations. Previously, the library only passed through IBKR API default values of empty prices being
-1
and empty sizes being0
and unset values beingnan
. These defaults are actually somewhat dangerous because in some circumstances, negative prices are valid, so if you only consume prices without checking "is this -1 a real value or not?" you can end up with unexpected results.Now, customizing your own empty/zero value defaults can greatly simplify your logic and improve code correctness instead of having to check for all combinations or price and size and unset possibilities everywhere.
Also, you can specify a default timezone for the objects to populate instead of UTC as well.
Here's a simple example of the new default setting mechanism, but you could also use custom objects for
EmptyPrice
orEmptySize
orUnsetValue
if you wanted.Additionally, there are more bug fixes and quality of life enhancements:
OrderState
objects (where all prices are just strings) now support conversion to direct numeric values instead.This discussion was created from the release v2.0.1.
Beta Was this translation helpful? Give feedback.
All reactions