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 4, 2024. It is now read-only.
Stakewars feedback:
nearshell always creates a folder of configuration named "neardev" on current directory after running "near login" command , when running nearshell on another folder without "neardev" folder, nearshell's login state would change to unlog, which would cause users to be confused .
Proposed solution is to store keys under .near (with the exception of development projects that keep their keys under neardev).
The text was updated successfully, but these errors were encountered:
Stakewars feedback:
nearshell always creates a folder of configuration named "neardev" on current directory after running "near login" command , when running nearshell on another folder without "neardev" folder, nearshell's login state would change to unlog, which would cause users to be confused .
Proposed solution is to store keys under .near (with the exception of development projects that keep their keys under neardev).
The text was updated successfully, but these errors were encountered: