Fix/gufm check syntax #3369
Merged
Fix/gufm check syntax #3369
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
REUPLOAD #2390 (rebase latest develop)
Fixes #1862
This PR is ready for review.
Risk
This PR makes minor API changes.
Testing Plan
Provide ATF tests
Summary
According to the issues when HMI sends request with String param with invalid characters we need to log corresponding error internally and respond with 'INVALID_DATA' to HMI.
The following RPCs do not have string params:
we do not have any changes for them
For RPC SDL.GetUserFriendlyMessage was added desired behaviour
OpenSDL do not consist SDL.GetDeviceConnectionStatus RPC, so this pull request add this RPC and expected behaviour for it when HMI sends request with String param with invalid characters.
UPDATES SINCE #2390
CLA