-
Notifications
You must be signed in to change notification settings - Fork 17
Align notification responses format #147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
scottinet
merged 16 commits into
develop
from
develop-110-align-notification-responses-format
Jan 23, 2017
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
4d5c67d
fixes #110 align notification response format
benoitvidis 83ace8e
fixes #146 align notification response format
benoitvidis dc04830
Merge branch 'develop-110-align-notification-responses-format' of git…
benoitvidis d8d945b
fix changelog issue #
benoitvidis 76ab186
eslint
benoitvidis 66792c8
Merge remote-tracking branch 'origin/develop' into develop-110-align-…
benoitvidis ac4f4d1
Merge remote-tracking branch 'origin/develop' into develop-110-align-…
benoitvidis bc9e51d
Merge branch 'develop' into develop-110-align-notification-responses-…
b21d3a6
Merge branch 'develop' into develop-110-align-notification-responses-…
9132621
Merge remote-tracking branch 'origin/master' into develop-110-align-n…
benoitvidis 6c70bce
Merge remote-tracking branch 'origin/factory-method-refactor' into de…
benoitvidis 7848ace
notifications format
benoitvidis 737ee24
Merge branch 'develop' into develop-110-align-notification-responses-…
38152bf
Merge remote-tracking branch 'origin/develop' into develop-110-align-…
benoitvidis 3ab2d14
fix webpack config + dev depency on should-sinon
benoitvidis f0f1841
Merge remote-tracking branch 'origin/develop' into develop-110-align-…
benoitvidis File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
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
File renamed without changes.
File renamed without changes.
File renamed without changes.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
--bail | ||
--require should-sinon | ||
--reporter spec | ||
--recursive |
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does not seem to match the PR description.
Here, the
result
field is replaced by auser
property, seemingly containing acount
property.Am I next to the plaque?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question for me, but I did not follow the discussion about that, so I may be wrong...
Can you either fix that, or fix the PR description, depending what is really wanted ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The initial PR description has been kept for history but the actual implementation matches the one we have aggreed on.
So, no result anymore, but a new field named as the new type property. In this case, it is normal we have a user.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the ref: here is the updated one: #147 (comment)