This repository has been archived by the owner on Jun 28, 2021. It is now read-only.
Ensure camelcaseKeys is never passed a non-object #1049
Merged
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.
Ensure camelcaseKeys is never passed a non-object
Currently, the
/api/v3/juzs
endpoint is 500ing, which causescamelcaseKeys
to be called withundefined
. According to sindresorhus/camelcase-keys#15, we should ensure we never callcamelcaseKeys
with something other than an object. Ideally, this is fixed on the BE where we fix the issue that is causing the BE to 500 but this will at least ensure the FE does not completely break and hang.I suspect this is also the reason why the homepage of the staging site is hanging (http://staging.quran.com/).
Checklist
package-lock.json