-
Notifications
You must be signed in to change notification settings - Fork 0
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
Groupname is required #10
Comments
GroupName is required by the publish command, but it's not required for some of the other commands. I'll check if I can make that property conditionally required or something. |
Looks like we cannot make an input parameter required only for certain scenario's, so doing this properly would require a breaking change which would involve separating out the group name used for publish and a different input for the other commands. Would rephrasing the text in the tooltip here suffice for now so that we make it clear that group name is required for publishing scenario's?. |
I think rephrasing would make it clearer. However, I probably wouldn't fill it in the first time because Azure DevOps doesn't prompt me that I have to fill it in. |
I've just released a new version of the extension which fixes a bug and I've modified the description of the group name field in the process. I'll keep this open to figure out a more permanent solution for this problem. |
The groupName property is required:
![image](https://user-images.githubusercontent.com/4221997/56131013-a7623b80-5f86-11e9-8cd7-f53dc0252c9b.png)
However, the task says that the property is optional:
![image](https://user-images.githubusercontent.com/4221997/56131091-d5e01680-5f86-11e9-9b3a-bfb0474a407b.png)
The text was updated successfully, but these errors were encountered: