-
Notifications
You must be signed in to change notification settings - Fork 490
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
TypeError: s.map is not a function in InvestigationBuilder component #8008
Comments
Hi, @coronasafe/care-frontend-maintainers, This issue has been automatically marked as stale because it has not had any recent activity. |
@khavinshankar Hey, I would like to fix this issue. Please assign it to me. |
I used the optional chaining method to avoid errors, but it ended up causing more issues. "Could you please clarify if 'is s' is referring to investigations?" |
Hi, @coronasafe/care-frontend-maintainers, This issue has been automatically marked as stale because it has not had any recent activity. |
hi @rithviknishad ,can you please assign this issue to me!. |
An error was encountered in the
InvestigationBuilder
component causing the JavaScript TypeError:s.map is not a function
. This error is likely due to attempting to call.map()
on a variables
that is not properly initialized as an array before this method call.Error Details
InvestigationBuilder.tsx
InvestigationBuilder
TypeError: s.map is not a function
3533b1853bd646609326b51cf152345a
Steps to Reproduce:
https://care.coronasafe.in/facility/0c95c7f0-e1d2-4aff-83fa-933cef60d3a8/patient/19adff46-588e-4072-89b3-a23ec1dec5fa/consultation/cc5ec4c3-94af-4fec-a954-fb9b7c45b89e/daily-rounds
s
variable.Potential Cause:
The variable
s
might be eitherundefined
or not an array at the time.map()
is called. This could be due to a failure in data fetching or data transformation before passing it to theInvestigationBuilder
.Suggested Fix:
s
is always initialized as an array.s
before applying array-specific methods like.map()
.This issue has occurred in a staging environment, so it's crucial to address it before the next production deployment to prevent user-facing errors and potential disruptions in service.
The text was updated successfully, but these errors were encountered: