-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add description field to script.json #823
Comments
The general idea was that verbs are first class citizens like any other app/plugin etc. Therefore it would be difficult (conceptionally) to add a different json for verbs. |
Yes, it's the same purpose as application.json -> when you click on it it displays the informations. |
Then I would suggest simply a "description" field in script.json. |
Ok for me. |
^^ Same time |
It should not only be for verbs but in general. |
I think we could even add a "conflict" field for listing conflicting verbs like winetricks does. |
Possible but probably hard to maintain (imagine e.g. a script is renamed). |
If a script is renamed, you have to update every script calling it... So I do not think a script will be renamed. |
Let's go for the description and then see what else we might need. |
I think that #361 targets the same problem. I don't think we require both issues. |
Then I would prefer "description" over "note". So in my opinion we can close #361. |
This file should contains files describing the verbs, for example:
Those informations should be displayed when someone wants to install a verb from the container tab for example.
The text was updated successfully, but these errors were encountered: