I am adding a new field (called 'Path') right above Schedule. I have concerns about it behavior and my idea includes two cases:
1) If field is empty plugin will still use NuGet.Config file from nuget.exe directory;
2) if user puts anything like 'NuGet.Config', '/Sources/NuGet.Config', 'Sources' or just '/' plugin will take NuGet.config file by the specified path, where root directory is the current workspace.
Is that good solution for that plugin?
Andrii Nikolaienko
added a comment - I am adding a new field (called 'Path') right above Schedule. I have concerns about it behavior and my idea includes two cases:
1) If field is empty plugin will still use NuGet.Config file from nuget.exe directory;
2) if user puts anything like 'NuGet.Config', '/Sources/NuGet.Config', 'Sources' or just '/' plugin will take NuGet.config file by the specified path, where root directory is the current workspace.
Is that good solution for that plugin?
I am adding a new field (called 'Path') right above Schedule. I have concerns about it behavior and my idea includes two cases:
1) If field is empty plugin will still use NuGet.Config file from nuget.exe directory;
2) if user puts anything like 'NuGet.Config', '/Sources/NuGet.Config', 'Sources' or just '/' plugin will take NuGet.config file by the specified path, where root directory is the current workspace.
Is that good solution for that plugin?