Move moments API from beta to public#111
Open
brunnjf wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
@miguelestrada @jarusso ready for review, pending the changes to actually move moments to public internally. |
miguelestrada
approved these changes
Aug 14, 2018
miguelestrada
left a comment
miguelestrada
left a comment
Contributor
There was a problem hiding this comment.
Will await indication that it is ok to merge.
mgwn
approved these changes
Aug 14, 2018
Collaborator
|
looks good but we need to add an entry to What's New as well for this |
Contributor
Author
|
Good catch. I will do that @jarusso The What's New entry includes a date, so I have it ready but have to wait until we are just about set to commit it. |
Contributor
|
@brunnjf bump |
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
4 participants
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.
1 of 2 steps to move moments API to public. This should wait until the internal changes to GraphQL have been made to make this public.
@UOKS FYI and for review