We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug Getting Location workspace file ('angular.json') could not be found while trying to serve application
Screenshots
Additional context Problem is, everytime it is trying to serve application from home directory where app doesn't exist. Hence command fails.
Proposed Solution There should be an option to specify root dir in serve tab and make application field mandatory. Once user enter root dir and application name, we can pass it as current working directory to the cli command. Note msg.dir here:- https://github.com/angular-klingon/klingon/blob/master/packages/klingon-server/terminal.js#L60
Related to #6
The text was updated successfully, but these errors were encountered:
Bug: Local workspace file ('angular.json') could not be found
6234a5a
Added root directory, made application field mandatory Fixes angular-klingon#72
bug(serve): Local workspace file ('angular.json') could not be found
82a369c
sumitparakh
No branches or pull requests
Describe the bug
Getting Location workspace file ('angular.json') could not be found while trying to serve application
Screenshots
Additional context
Problem is, everytime it is trying to serve application from home directory where app doesn't exist. Hence command fails.
Proposed Solution
There should be an option to specify root dir in serve tab and make application field mandatory. Once user enter root dir and application name, we can pass it as current working directory to the cli command. Note msg.dir here:-
https://github.com/angular-klingon/klingon/blob/master/packages/klingon-server/terminal.js#L60
Related to #6
The text was updated successfully, but these errors were encountered: