-
Notifications
You must be signed in to change notification settings - Fork 113
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
List of FD / DK contest types that we can implement #112
Comments
I'll take on NFL/NHL showdown and FanDuel MVP |
Hijacking this to ask if we want to implement more lineup constraints than just lock/ban for tiers. IMO its not really worth the effort. |
Also, we can implement the DK NFL tiers with the pickem code |
@sharkiteuthis Going to grab NFL showdown to make a blueprint for the future. Some trickiness I'll address but obviously weigh in with opinions:
Don't think implementation is hard, it's more how should the public facing API look. |
look at the feature branch i have for NFL showdown, it's mostly done. the remaining items:
|
Awesome, I’ll hold off
…On Tue, Jan 1, 2019 at 5:40 PM Tom Dodson ***@***.***> wrote:
look at the feature branch i have for NFL showdown, it's mostly done.
the remaining items:
- add ban captains
- test group constraints for showdowns
- add showdown team filters
- test with exposure
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#112 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGqt9PAj033qSYIs719keAsvyK5Ux7Hvks5u--PNgaJpZM4ZfnbY>
.
|
If you want to build on that branch, feel free, I won't be able to look at it again until at least tomorrow. |
Cool, I'll take a look tonight and commit if I have anything good to add. Will open PR just so it's out there. |
Anyone reading this - feel free to add here. These are generally pretty easy so PRs welcome. If you pick any of the below up, you need at a minimum:
RuleSet
name and any other relevant usage info if applicableThe list
README
) (DK)The text was updated successfully, but these errors were encountered: