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

New - don't add unparsed options as the name #1085

Closed
ferventcoder opened this issue Dec 11, 2016 · 0 comments
Closed

New - don't add unparsed options as the name #1085

ferventcoder opened this issue Dec 11, 2016 · 0 comments
Assignees
Milestone

Comments

@ferventcoder
Copy link
Member

Related to #983, don't add unparsed options as the name of the package

@ferventcoder ferventcoder added this to the 0.10.4 milestone Dec 11, 2016
@ferventcoder ferventcoder self-assigned this Dec 11, 2016
ferventcoder added a commit that referenced this issue Dec 11, 2016
If there are unparsed options or properties that are passed, do not
use those as the name. Only add the name when it is definitely a name
and doesn't start with a "-" or contain "=".
ferventcoder added a commit that referenced this issue Dec 11, 2016
* stable:
  (GH-1085) do not add options/properties as name
  (doc) update generated docs
  (doc) Ensure command reference urls
  (GH-961) Add source link comments to top of files
  (GH-1075) Add Architect license type SKU
  (doc) update licensed changelog
Apteryx0 pushed a commit to Apteryx0/choco that referenced this issue Jan 23, 2017
If there are unparsed options or properties that are passed, do not
use those as the name. Only add the name when it is definitely a name
and doesn't start with a "-" or contain "=".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants