Repository navigation
Properly split attribute strings, even if they have sub attributes - #15
Merged
Merged
Conversation
The SDK improperly procesess both search strings and server responses for said search strings, if the original search string contains filters between '[]' and said filter contain a '.'. Example: Original search string: History[Status.Name='Done'] This will be processed as ["History[Status", "Name='Done']"]
kunzimariano
added a commit
that referenced
this pull request
Aug 2, 2014
-Added string_utils module with the function split_attribute. - Replaced the string split on dots for the new function. - Added tests for split_attribute.
Contributor
|
Thanks for your contribution, we accepted your pull request. Let us know if the changes we made are still valid for the issues you were having. |
This file contains hidden or 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.
The SDK improperly procesess both search strings and server
responses for said search strings, if the original search string
contains filters between '[]' and said filter contain a '.'.
Example:
Original search string: History[Status.Name='Done']
This will be processed as ["History[Status", "Name='Done']"]