Bug, security code removing left zero and broken tests #1
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
lfreneda
pushed a commit
that referenced
this pull request
Apr 10, 2014
Bug, security code removing left zero and broken tests
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.
When a user buys with a security code that starts with zero, Cielo returns the error below:
Cielo.Responses.Exceptions.ResponseException: O XML informado n o valido: - string value '11' does not match pattern for type of codigo-seguranca element in DadosCartao in namespace http://ecommerce.cbmp.com.br: ''
This error occurs because the user input is, for example, 011 and the variable security code is a type int, so the left zero is removed sending only 11 to Cielo.