When Creating Segment, Ensure Only ID is Returned #62
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
`api_call.static_segment_add` returns a Hash, not the segment's ID, so when a segment is created, `@segment_id` can contain an unexpected Hash.
|
CI spec failures seem to have been caused by 4681d8a. Shall I update the specs to reflect the change? |
|
Thanks ddubya! Yes, updating that spec would be helpful (/cc: @braidn ) |
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.
api_call.static_segment_addreturns a Hash, not the segment's ID, so when a segment is created,@segment_idcan contain an unexpected Hash, which causes an exception to be thrown when, say, subscribing a customer. Bad news bears!