Do not require entry fees for competitions in multiple countries. #3755
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AlbertoPdRF
approved these changes
Dec 29, 2018
jfly
force-pushed
the
do-not-require-entry-fees-for-competitions-in-multiple-countries
branch
from
f92e3e5 to
d91b65c
Compare
This just came up for FMC Europe, a competition which has different registration requirements per venue. Rather than requiring the user to specify an inaccurate number, we'd rather have these values be NULL (unknown) in our database. Note: This does not detect competitions in multiple venues within the same country (such as FMC USA). We can add support for that later if we decide we want to.
jfly
force-pushed
the
do-not-require-entry-fees-for-competitions-in-multiple-countries
branch
from
d91b65c to
1c2fbac
Compare
jfly
deleted the
do-not-require-entry-fees-for-competitions-in-multiple-countries
branch
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This just came up for FMC Europe, a competition which has different
registration requirements per venue. Rather than requiring the user to
specify an inaccurate number, we'd rather have these values be NULL
(unknown) in our database.
Note: This does not detect competitions in multiple venues within the
same country (such as FMC USA). We can add support for that later if we
decide we want to.