Skip to content

Multiround #1452

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

Merged
merged 23 commits into from
Dec 20, 2022
Merged

Multiround #1452

merged 23 commits into from
Dec 20, 2022

Conversation

jmgasper
Copy link
Collaborator

Multi-round challenge launching from WM

jmgasper and others added 23 commits September 2, 2022 11:22
#1412

1. A "project" contains "status" field , this status field can be "active"/"in_review"

2. A "project" also has a billingAccount mapped.

3. Application makes a GET call with billingAccount id to get billingAccount details. and response of it is this screenshot https://imgur.com/cU3s4yU

4. response has "active" boolean field and enddate field which is correctly utilised in reducer code to set the flag "isBillingAccountExpired". check this screenshot https://imgur.com/l5nyxbt

5. now this "isBillingAccountExpired" flag is used like this. check screenshot https://imgur.com/mjDhbAF

6. when "isBillingAccountExpired" is true, we show hardcoded "INACTIVE" which is correct.

7. but when "isBillingAccountExpired" is false , we show "status" field of "project" which is wrong, because we need to show whether billingAccount is active or not.

8. hence "status" field of project can be active/inReview , thats why u see "IN_REVIEW" in UI,

9. hence my solution/approach is that flag "isBillingAccountExpired" is already there which clearly indicates active/inactive, hence i hardcoded "ACTIVE" in code because it is obvious.
[Security][Clickjacking]-Adding X-Frame-Options and X-Frame-Options h…
# Conflicts:
#	.circleci/config.yml
#	src/components/ChallengeEditor/ChallengeView/index.js
#	src/components/ChallengeEditor/index.js
#	src/config/constants.js
@jmgasper jmgasper merged commit af2ee4f into master Dec 20, 2022
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.

4 participants