NativeScript / NativeScript/nativescript-cli
Contextual Logging
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
There are some command specific messages that look strange both when the NativeScript CLI is used as a library and from the command line. For example, take a look at this change.
Describe the solution you'd like
A possible solution is defining an error object instead of using strings. The object could contain something like a CLI specific message and the logger could handle the error messages based on the current CLI usage.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the files changed in PR #4063 and tracing how command-specific messages reach the logger when the NativeScript CLI runs from the command line versus as a library. Done means contextual error messages are represented and handled differently for those two usage modes, as described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100