You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I often make the mistake of saying something like (get-contract-details ... { :security-type :equity }) when I should say :type :equity. I get an error message from IB, but it's not immediately obvious what's wrong.
Maybe map->, the thing that's used internally to convert from maps like the one you give for the contract parameter to get-contract-details should warn or fail if there are any keys in your map that aren't going to be translated, giving a list of the keys that will be.
I originally didn't think this would be a good idea, thinking you might want to have contract maps with extra stuff that you wanted to use to keep track of something else, but that doesn't seem that useful anymore.
Alternatively, there are a couple of common mistakes (like :type not being set or one of :symbol/:local-symbol not being set. We could just warn about these things.
The text was updated successfully, but these errors were encountered:
I often make the mistake of saying something like
(get-contract-details ... { :security-type :equity })
when I should say:type :equity
. I get an error message from IB, but it's not immediately obvious what's wrong.Maybe
map->
, the thing that's used internally to convert from maps like the one you give for the contract parameter toget-contract-details
should warn or fail if there are any keys in your map that aren't going to be translated, giving a list of the keys that will be.I originally didn't think this would be a good idea, thinking you might want to have contract maps with extra stuff that you wanted to use to keep track of something else, but that doesn't seem that useful anymore.
Alternatively, there are a couple of common mistakes (like
:type
not being set or one of:symbol
/:local-symbol
not being set. We could just warn about these things.The text was updated successfully, but these errors were encountered: