-
Notifications
You must be signed in to change notification settings - Fork 89
Conversation
(https://www.topcoder.com/challenge-details/30057891/?type=develop) Verification guide: docs/Verification_Guide-Improve Challenge Visibility Control.doc
actions/challenges.js
Outdated
}, function (res, cb) { | ||
if (res.exists.length === 0 || Boolean(res.exists[0].is_studio) !== isStudio) { | ||
// If the record with this callengeId doesn't exist in contest_eligibility table |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TheOsch it is possible that there is no records, which mean the challenge is pubic group.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
@TheOsch for https://github.com/appirio-tech/tc-api/blob/master/actions/challengeRegistration.js#L81, can we do the similar check as validation? |
We discussed it with Tony Jefts yesterday. In fact, the validateChallenge function (where the link in the challenge spec points to) is used only in actions that get checkpoints. |
@TheOsch I see |
@skyhit I looked at the list of actions at routes.js and wrote done all that look like in scope. When you'll have time would you please briefly look at this list and prompt me if there are some actions in the list that have nothing in common with our task, or maybe I missed some? I think you know the API much better than I, and it will save us a lot of time. get: [ |
@ajefts since we are using v3 apis, I think some of the apis above are not used anymore. |
@TheOsch Where does TC_API_V3_URL get read from? |
@skyhit Yes, let's review the list when you have time. We won't need to update all of those. |
From the environment. For example, one can run the command like
Meanwhile i'll work on challengeRegistration.js . Already began working on it, will commit tomorrow. |
The eligibility check routine is now in challengeHelper and can be added anywhere by a couple of simple lines of code.
Committed. Sorry for a delay. What's next? |
@TheOsch we will test the current logic in dev, then we can decide the next step |
@TheOsch can you future make the changes to |
@TheOsch mainly logic related to the following check |
@skyhit Easily. Changing both actions (getSoftwareChallenge and getRegistrants) will take one day, I can make it by tomorrow. |
* Improve challenge visibility control (#501) * IMPROVE CHALLENGE VISIBILITY CONTROL (https://www.topcoder.com/challenge-details/30057891/?type=develop) Verification guide: docs/Verification_Guide-Improve Challenge Visibility Control.doc * Restoring an accidentially modified file * Fixed the case with a challenge that doesn't have eligibility * Shared the eligibility verification with challengeRegistration. The eligibility check routine is now in challengeHelper and can be added anywhere by a couple of simple lines of code. * improve the query * update query for groups (#502) * Update queries (#503) improve logging for v3 api call * should use externalToken field name
* Improve challenge visibility control (#501) * IMPROVE CHALLENGE VISIBILITY CONTROL (https://www.topcoder.com/challenge-details/30057891/?type=develop) Verification guide: docs/Verification_Guide-Improve Challenge Visibility Control.doc * Restoring an accidentially modified file * Fixed the case with a challenge that doesn't have eligibility * Shared the eligibility verification with challengeRegistration. The eligibility check routine is now in challengeHelper and can be added anywhere by a couple of simple lines of code. * improve the query * update query for groups (#502) * Update queries (#503) improve logging for v3 api call * should use externalToken field name * update queries for group checking * Improve challenge visibility control: getChallenge and getRegistrants (#504) * IMPROVE CHALLENGE VISIBILITY CONTROL (https://www.topcoder.com/challenge-details/30057891/?type=develop) Verification guide: docs/Verification_Guide-Improve Challenge Visibility Control.doc * Restoring an accidentially modified file * Fixed the case with a challenge that doesn't have eligibility * Shared the eligibility verification with challengeRegistration. The eligibility check routine is now in challengeHelper and can be added anywhere by a couple of simple lines of code. * Improve challenge visibility control: getChallenge and getRegistrants * revert commit
* Improve challenge visibility control (#501) * IMPROVE CHALLENGE VISIBILITY CONTROL (https://www.topcoder.com/challenge-details/30057891/?type=develop) Verification guide: docs/Verification_Guide-Improve Challenge Visibility Control.doc * Restoring an accidentially modified file * Fixed the case with a challenge that doesn't have eligibility * Shared the eligibility verification with challengeRegistration. The eligibility check routine is now in challengeHelper and can be added anywhere by a couple of simple lines of code. * improve the query * update query for groups (#502) * Update queries (#503) improve logging for v3 api call * should use externalToken field name * update queries for group checking * Improve challenge visibility control: getChallenge and getRegistrants (#504) * IMPROVE CHALLENGE VISIBILITY CONTROL (https://www.topcoder.com/challenge-details/30057891/?type=develop) Verification guide: docs/Verification_Guide-Improve Challenge Visibility Control.doc * Restoring an accidentially modified file * Fixed the case with a challenge that doesn't have eligibility * Shared the eligibility verification with challengeRegistration. The eligibility check routine is now in challengeHelper and can be added anywhere by a couple of simple lines of code. * Improve challenge visibility control: getChallenge and getRegistrants * revert commit
No description provided.