Feat/practice interview questions #163
Open
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
…e from BE with relationships questions added to the jobApplications serializer.
…at/practice-interview-questions
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.
Type of Change
Description
This PR creates a new component for practice interview questions. At the moment the component renders dummy questions, but the fetch request has been built to send job descriptions to the backend to generate practice interview questions from OpenAI. The fetch request will not work until the BE branch feat/interview_questions_route is merged, so to test this functionality, you will need to fetch the BE branch feat/interview_questions_route.
Motivation and Context
This PR is the first step to implement the API call to OpenAI to populate practice interview questions. This PR is a skeleton with dummy questions.
Related Tickets
A task card #162 has been created to finish this component by refactoring the fetch request and writing Cypress tests that reflect the fetch request and potential sad paths and edge cases.
Screenshots (if appropriate):
Added Test?
Checklist: