-
Notifications
You must be signed in to change notification settings - Fork 28
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
feat: Receive user name instead of customer intent for new terms UI #1094
base: main
Are you sure you want to change the base?
Conversation
2a07b3a
to
adea2a2
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #1094 +/- ##
==========================================
+ Coverage 96.02% 96.12% +0.10%
==========================================
Files 831 829 -2
Lines 19563 19538 -25
==========================================
- Hits 18785 18781 -4
+ Misses 778 757 -21
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. 📢 Thoughts on this report? Let us know! |
❌ 6 Tests Failed:
View the top 3 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
✅ All tests successful. No failed tests were found. 📣 Thoughts on this report? Let Codecov know! | Powered by Codecov |
❌ 6 Tests Failed:
View the top 3 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
and input.customer_intent not in valid_customer_intents | ||
): | ||
raise ValidationError("Invalid customer intent provided") | ||
print("qwerty input: ", input) |
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.
@@ -5,5 +5,6 @@ type User { | |||
student: Boolean! | |||
studentCreatedAt: DateTime | |||
studentUpdatedAt: DateTime | |||
# this will no longer be updated from the UI with Appless |
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.
we can't delete the customerIntent: String
line?
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.
Would this have any chance of breaking anything in a transition period? I wanted to double check here to make sure it was safe. Would you suggest rolling out gazebo changes first or codecov-api first since we're removing customerIntent
but adding name
on the SaveTermsAgreementInput side
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.
Wait so if you are changing the interface of SaveTermsAgreementInput then would gazebo not break when this change is deployed? Assuming gazebo is currently using save terms agreement
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.
I think it would... it sounds like I would need to change this to be a phased rollout in that case. I think I would need to add back customerIntent
for now and then just loosen the validations on it as we can't expect it to be passed through from the new UI form. Does that sound accurate?
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.
Yeah sounds about right.
- Accept either name or customer intent
- Switch gazebo to use name
- Remove customer intent from api
@user_bindable.field("customerIntent") | ||
def resolve_customer_intent(user: Owner, info) -> str: | ||
def resolve_customer_intent(user: Owner, info: GraphQLResolveInfo) -> Optional[str]: |
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.
similarly should this be deleted?
Purpose/Motivation
What is the feature? Why is this being done?
New onboarding changes for pre-PAT appless to make it easier and more clear for users to sign up. We are changing up the required information that a user must fill out to complete onboarding. We will no longer be asking for customer intent and for the user to select a default organization in step that follows this screen.
Links to relevant tickets
codecov/engineering-team#3174
Changes related to the UI changes designated in this Figma: https://www.figma.com/design/SsoxtY2SB73l0wiLbJ8FhZ/GH-2092?node-id=2288-16704&t=sMCRUMT3J1bwIct1-1
What does this PR do?
For the onboarding page, we are:
Notes to Reviewer
Anything to note to the team? Any tips on how to review, or where to start?
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.