Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for FOK & IOC limit orders #15

Conversation

rupurt
Copy link
Collaborator

@rupurt rupurt commented May 25, 2018

Builds upon #14

@rupurt rupurt mentioned this pull request Jun 5, 2018
@rupurt rupurt force-pushed the fill-or-kill-and-immediate-or-cancel-orders branch from 01c50e5 to 763b8f7 Compare June 6, 2018 15:25
@rupurt rupurt force-pushed the fill-or-kill-and-immediate-or-cancel-orders branch 3 times, most recently from c940af2 to 5bf73b5 Compare June 19, 2018 01:40
@rupurt rupurt force-pushed the fill-or-kill-and-immediate-or-cancel-orders branch from 5bf73b5 to d2d7332 Compare June 23, 2018 16:49
@rupurt
Copy link
Collaborator Author

rupurt commented Jun 23, 2018

@dvcrn this one is now ready that we've merged #14

@dvcrn
Copy link
Owner

dvcrn commented Jun 26, 2018

Looks good to me!

What do you think about using constant-like structures for the time in force values? Something like this

@rupurt
Copy link
Collaborator Author

rupurt commented Jun 26, 2018

@dvcrn do you mean for the defaults? Do you mind adding an example so I can grok your suggestion a little more.

@dvcrn
Copy link
Owner

dvcrn commented Jun 28, 2018

I guess not so important right now. I'll merge this first and then we can think about it at a later point 👍

Thanks a ton of the contribution 😄

@dvcrn dvcrn merged commit 189f785 into dvcrn:master Jun 28, 2018
@rupurt rupurt deleted the fill-or-kill-and-immediate-or-cancel-orders branch June 28, 2018 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants