You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Don't do project discovery when explicitly defined
Previously, the project path discovery and type detection were done even when the user's settings explicitely defined
these things. When the contents of the given path did not contain something slightly resembling a project of the given
type, the process exited.
That behavior is the only one possible when a project is not explicitely defined by the user, but in the case of an
explicit definition, this is an unnecessary short circuiting of the process. The checks can still be run. This will
result in the same exit status as before, but the check results may provide the user with helpful information about why
their project is invalid.
// If targetPath is a file, targetPath itself is the project, so it's only necessary to determine/verify the type.
58
58
iftargetPath.IsNotDir() {
59
59
logrus.Debug("Projects path is file")
60
-
// The filename provides additional information about the project type. So rather than using isProject(), which doesn't make use this information, use a specialized function that does.
// The filename provides additional information about the project type. So rather than using isProject(), which doesn't make use this information, use a specialized function that does.
0 commit comments