Removing dot from end of SIM_SWAP.UNKNOWN_PHONE_NUMBER response message. This is to align with other response messages. #62
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.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
This is a tiny change! Removing only 1 character from the spec.
Have removed the dot at the end of the message for SIM_SWAP.UNKNOWN_PHONE_NUMBER.
i.e.
"SIM Swap can't be checked because the phone number is unknown."
has been changed to"SIM Swap can't be checked because the phone number is unknown"
(notice that the dot is removed at the end of the message).This is simply to align the SIM_SWAP.UNKNOWN_PHONE_NUMBER message with the other non-200 response messages. They all lack the dot at the end of the message. For example, "Client does not have sufficient permissions to perform this action"
Which issue(s) this PR fixes:
I did not create an issue for this - it seemed too small to raise an issue for. I can raise one if required.
Special notes for reviewers:
I was reviewing the existing spec in context of GSMA certification/testing and noticed the discrepancy.
Changelog input
Additional documentation
N/A