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
Currently, for invoking Parvaj, you must be in the project root. This could be annoying for some, e.g. one is using a console-based text editor like Vim, so he may keep moving around directories.
If you are using Parvaj and want this to be implemented, react this thread with a thumbs-up.
The text was updated successfully, but these errors were encountered:
One obvious solution is to crawl up the directories until we find the project root. However, there must be a way to know we reached it.
A possible solution to this is to have a file (e.g. parvaj.json or parvaj.yml, which might be used for future configurations as well) there, and scan for it everytime we go up in the path. This could be either created manually or automatically, however, being created automatically needs to have an initial successful Parvaj invocation in the project root.
Another way is to have a global configuration file to specify root of known projects. Like the previous, it could be specified either manually or automatically.
Currently, for invoking Parvaj, you must be in the project root. This could be annoying for some, e.g. one is using a console-based text editor like Vim, so he may keep moving around directories.
If you are using Parvaj and want this to be implemented, react this thread with a thumbs-up.
The text was updated successfully, but these errors were encountered: