-
Notifications
You must be signed in to change notification settings - Fork 7
fix(datatrak): RN-1490: survey response export containing User question #6540
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
Conversation
Summary of ChangesHello @jaskfla, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request addresses a bug where survey response exports did not correctly display answers for questions of type Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
| surveyScreenComponent: SurveyScreenComponent, | ||
| surveyResponse: SurveyResponse, | ||
| ) => { | ||
| ): React.ReactNode => { |
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.
Catch this type of error at build time instead
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.
Code Review
This pull request adds support for the User question type in the survey response export. The changes are well-contained within the Question.tsx component. My review includes a couple of suggestions to improve code robustness and maintainability, particularly around styling and data access patterns.
|
bugbot run |
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.
✅ Bugbot reviewed your changes and found no bugs!
c686df6 to
071537c
Compare
| return <StyledAvatar variant="square" src={answer} />; | ||
| } | ||
| case QuestionType.User: | ||
| return (answer as DatatrakWebSubmitSurveyResponseRequest.UserAnswer).name; |
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.
Bug: User Answer Fallback Needs Consistency
The QuestionType.User case assumes the answer has a name property but doesn't handle cases where it might be missing or undefined. If the UserAnswer object exists but lacks a name property, the function returns undefined instead of a fallback like other question types. Consider adding a fallback to answer itself or <em>No answer</em> when name is nullish.
chris-bes
left a comment
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.
lgtm
RN-1490 issue 5