Ensure error message stringified safely #692
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.
Previously,
api.common.response.err()in api-engine was used in two contexts:Exception.argsfrom the API engine, which is a Python tuple.Since JavaScript’s template strings call
.toString()on non‑string values, passing a tuple resulted in[object Object]in the UI.This change normalizes the error payload so that:
JSON.stringify().String().As a result, all error messages should display correctly in the frontend without
[object Object]artifacts.