fix(executeATCCheck): correctly escape namespaces #5275
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.
Description
The ATC check failed when the name of a development object included a namespace. Prior to this change, the generated request body looked like this:
Due to the unescaped slashes in the namespace, the SAP system failed with a 400 Bad Request error:
By ensuring the namespaces are properly escaped (e.g.
%2FABC%2FMY_TABLE
) for all object types, the ATC check now works as expected. However, for classes this issue was already fixed in commit 4ff5271 (gCTSExecuteABAPQualityCheck_namespace_objects (#4623), 2023-10-11).Checklist