Omit probability when serializing opportunity #82
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
|
Thanks @whitecl! It seems we are missing |
|
If not, no problem. I can also add it. |
| @@ -157,6 +157,18 @@ | |||
| end | |||
| end | |||
|
|
|||
| describe "#to_capsule_json" do | |||
| let(:opportunity) { Fabricate.build(:opportunity, value: 23.0, currency: 'USD') } | |||
There was a problem hiding this comment.
Line is too long. [85/80]
0d3140d to
3bd00bd
Compare
|
Added, let me know if this is what you were looking for. |
|
Looks great. Just one little thing; It would be cool if you could also assert |
|
Great! |
mattbeedle
added a commit
that referenced
this pull request
Sep 30, 2014
Omit probability when serializing opportunity
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.
I get the following when attempting to send updates to an Opportunity, even when the CapsuleCRM::Opportunity has no modifications.
CapsuleCRM::Errors::BadRequest:
value not formatted as a number
I've found that omitting the probability key from the update json amends this.