-
Notifications
You must be signed in to change notification settings - Fork 10
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
Setup basic route/view/controller for mentee application states #447
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Josh Smith <[email protected]>
Co-authored-by: Josh Smith <[email protected]>
Co-authored-by: Natblow <[email protected]>
Co-authored-by: Natblow <[email protected]>
Co-authored-by: Natblow <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #447 +/- ##
=======================================
Coverage 99.26% 99.27%
=======================================
Files 219 220 +1
Lines 3393 3437 +44
=======================================
+ Hits 3368 3412 +44
Misses 25 25 ☔ View full report in Codecov by Sentry. |
config/locales/views/user_mentee_applications/mentee_application_states/en.yml
Outdated
Show resolved
Hide resolved
end | ||
|
||
def next_state | ||
user_mentee_application.mentee_application_states.where('created_at > ?', created_at).order(:created_at).first |
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.
These methods could arguably go on the user_mentee_application
, but it'd have to accept a parameter for the state. This is one thing I'm not too sure about.
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.
these are fine for now
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.
One change related to the en.yml
file.
end | ||
|
||
def next_state | ||
user_mentee_application.mentee_application_states.where('created_at > ?', created_at).order(:created_at).first |
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.
these are fine for now
config/locales/views/user_mentee_applications/mentee_application_states/en.yml
Outdated
Show resolved
Hide resolved
Co-authored-by: Natblow <[email protected]>
Co-authored-by: Natblow <[email protected]>
Co-authored-by: Natblow <[email protected]>
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.
Some comments related to the copy we show people at each stage of the process
|
||
<p>You have been sent an email with a coding challenge. This should take you no more than 2-3 hours to complete.</p> | ||
|
||
<!-- TODO: fill in more content here --> |
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.
Do we want more copy here?
@@ -0,0 +1,3 @@ | |||
<h3>Coding Challenge Approved</h3> | |||
|
|||
<!-- TODO: do we need this step anymore? It's not outlined in the notion --> |
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.
This step is not in the notion outline for this feature. Do we want it?
|
||
<p>You have submitted your solution to our coding challenge. We will contact you after our team has reviewed your work.</p> | ||
|
||
<!-- TODO: fill more content here --> |
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.
Does this need any more copy?
@@ -0,0 +1,3 @@ | |||
<h3>Phone Screen Completed</h3> | |||
|
|||
<!-- This is another status I'm not sure we need? --> |
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.
Don't think we need this?
@@ -0,0 +1,5 @@ | |||
<h3>Phone Screen</h3> | |||
|
|||
<p>We would like to schedule a zoom call with you. This call is a quick interview with one of our senior members. It will last about 30 minutes. We will have read your application and reviewed your code. The ideal call is an informal conversation about your goals and your coding journey. There will also be an opportunity for you to ask us questions as well.</p> |
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.
Maybe this open with something about how we reviewed their code challenge and liked it?
|
||
<p>You have withdrawn your application to the Agency.</p> | ||
|
||
<!-- TODO the notion references links? What might those be? --> |
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.
Notion references different links that we could give the user here. What did people have in mind for this?
What's the change?
applications#index
rather than the application itselfWhat key workflows are impacted?
Viewing application state for applicants
Highlights / Surprises / Risks / Cleanup
Going to mention some highlights in some review comments
Potential surprise: we're kicking the full styling to a different PR.
Another potential surprise: we currently only have the text content for the
application_received
state. This is so we can confirm this PR's approach to this is the one we want to go with.Demo / Screenshots
Issue ticket number and link
Closes #442
Checklist before requesting a review
Please delete items that are not relevant.