Resolve CodeQL query alert 57

[roslynwythe]

Prerequisite

1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page.
2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We need to analyze the query "Use of returnless function" which appears in the CodeQL alert 57 then either recommend dismissal of the alert or update code to resolve the alert.

Action Items

• DO NOT DISMISS ANY ALERTS. Dismissal of alerts should be done by dev leads only after review of the recommendation
• Browse to the links in the following two Action Item and read the contents. Click "See More" to view Recommendations, Examples and References.
• https://github.com/hackforla/website/security/code-scanning/57
• In a comment in this issue, add your analysis and recommendations. For each alert, the recommendation can be one of the following: dismiss as test, dismiss as false positive, dismiss as won't fix, or update code.
• If the recommendation is to update code:
  • create an issue branch and proceed with the code update
  • Use docker to test locally, ensuring that there are no changes to any affected webpage(s)
  • proceed with pull request in the usual manner
• If the recommendation is to dismiss, describe your reason for dismissal in the comment, then move the issue to Questions/In Review and apply the label ready for dev lead.

For merge team/dev lead

• If recommendation to dismiss is approved, dismiss the alert with a comment, then close the issue as completed.
• When this issue is closed please check it off (under "Issues") in Create issues to resolve all open CodeQL alerts #5159. If all child issues are closed, close Create issues to resolve all open CodeQL alerts #5159 as completed.

Resources/Instructions

• GitHub CodeQL documentation
• This issue is part of Create Issues for Analysis of CodeQL alerts #5060

[github-actions]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels