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
{{ message }}
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
One of the information that tools are going to require from users is the project name.
Tooling will usually ask users to provide a name. But It would be nice if Alizer provides project name detection that could be used as the default project name.
It would be nice if Alizer provides a function that detects the project name from the information (source code) available. (maybe something like recognizer.SuggestName(path))
Most of the languages already have a place that contains the project name.
JavaScript: name field in package.json
Java (Maven): artifactId in pom.xml
If Alizer can't detect the project name or the language ecosystem doesn't have a standard way to define a name fallback would be the directory name.
One of the information that tools are going to require from users is the project name.
Tooling will usually ask users to provide a name. But It would be nice if Alizer provides project name detection that could be used as the default project name.
It would be nice if Alizer provides a function that detects the project name from the information (source code) available. (maybe something like
recognizer.SuggestName(path)
)Most of the languages already have a place that contains the project name.
name
field inpackage.json
artifactId
inpom.xml
If Alizer can't detect the project name or the language ecosystem doesn't have a standard way to define a name fallback would be the directory name.
the related odo issue redhat-developer/odo#5847
The text was updated successfully, but these errors were encountered: