Preference page for dotnet path and future developments #99
Assignees
Labels
Comments
LucasBullen
pushed a commit
to LucasBullen/aCute
that referenced
this issue
Nov 15, 2017
Signed-off-by: Lucas Bullen <lbullen@redhat.com>
LucasBullen
pushed a commit
to LucasBullen/aCute
that referenced
this issue
Nov 15, 2017
Will stop users from using features requiring dotnet if the path is not found and point them towards the preference page Signed-off-by: Lucas Bullen <lbullen@redhat.com>
LucasBullen
pushed a commit
to LucasBullen/aCute
that referenced
this issue
Nov 17, 2017
Will stop users from using features requiring dotnet if the path is not found and point them towards the preference page Signed-off-by: Lucas Bullen <lbullen@redhat.com>
mickaelistria
pushed a commit
that referenced
this issue
Nov 18, 2017
Will stop users from using features requiring dotnet if the path is not found and point them towards the preference page Signed-off-by: Lucas Bullen <lbullen@redhat.com>
|
Fixed with ff46e87 . Thanks @LucasBullen for this important addition! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As brought up in Issue #94, The need for a preferences page where users can input the path to the
dotnetcommand location is highly valued. This page would also allow for easier customization of future developments.The scope of this enhancement would be:
Contribution of a preference to configure the
dotnetpath, a preference initializer and a preference page designed for simple addition of new preferences.The text was updated successfully, but these errors were encountered: