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.
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
code refator #80
code refator #80
Changes from all commits
e623f06
78270e4
11be254
6ab05e0
46ca722
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
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.
Consider simplifying the logic in
formatTranslationMessages
to enhance readability. Using a ternary operator directly might be more straightforward than using a condition object.Committable suggestion
Check warning on line 11 in app/utils/apiUtils.js
GitHub Actions / Coverage annotations (🧪 jest-coverage-report-action)
🌿 Branch is not covered
Check warning on line 17 in app/utils/apiUtils.js
GitHub Actions / Coverage annotations (🧪 jest-coverage-report-action)
🧾 Statement is not covered
Check warning on line 18 in app/utils/apiUtils.js
GitHub Actions / Coverage annotations (🧪 jest-coverage-report-action)
🧾 Statement is not covered
Check warning on line 18 in app/utils/apiUtils.js
GitHub Actions / Coverage annotations (🧪 jest-coverage-report-action)
🌿 Branch is not covered
Check warning on line 31 in app/utils/apiUtils.js
GitHub Actions / Coverage annotations (🧪 jest-coverage-report-action)
🌿 Branch is not covered
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.
The transformation logic in
createApiClientWithTransForm
usesset
andmapKeysDeep
effectively for handling API response data. However, ensure this part of the code is covered by tests to prevent potential issues with data handling.Would you like assistance in creating unit tests for this transformation logic?
Check warning on line 38 in app/utils/apiUtils.js
GitHub Actions / Coverage annotations (🧪 jest-coverage-report-action)
🧾 Statement is not covered
Check warning on line 38 in app/utils/apiUtils.js
GitHub Actions / Coverage annotations (🧪 jest-coverage-report-action)
🧾 Statement is not covered
Check warning on line 38 in app/utils/apiUtils.js
GitHub Actions / Coverage annotations (🧪 jest-coverage-report-action)
🕹 Function is not covered
Check warning on line 39 in app/utils/apiUtils.js
GitHub Actions / Coverage annotations (🧪 jest-coverage-report-action)
🌿 Branch is not covered
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.
Similarly, the request transformation logic is well implemented using
set
andmapKeysDeep
. Coverage for this function should also be ensured.I can help with writing tests for this part as well. Let me know if you need it.