Skip to content
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

graph: output warnings to communicate breaking changes in the near future #7784

Merged
merged 5 commits into from
Nov 10, 2018

Conversation

yugangw-msft
Copy link
Contributor

For #1150

  • The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

  • I adhere to the Command Guidelines.

' 100 objects to avoid long waiting. You can still use "--all" for old behavior, though it is much'
' recommended to avoid it')
' 100 objects to avoid long waiting. You can still use "--all" for old behavior,'
' though it is much recommended to avoid it')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommended wording:
"In a future release, if no filter arguments are provided, CLI will output only the first 100 objects to minimize wait times. You can still use --all for the old behavior, though it is not recommended."

@yugangw-msft yugangw-msft merged commit 8251f70 into Azure:dev Nov 10, 2018
@yugangw-msft yugangw-msft deleted the spwarn branch December 28, 2018 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants