Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. ItΒ collects links to all the places you might be looking at while hunting down a tough bug.
And, if youβre still stuck at the end, weβre happy to hop on a call to see how we can help out.
nx format:check --verbose should actually show what is wrong with a file
See original GitHub issueDescription
As nx format:check shows which files fail the format check but not what is actually wrong in them, I would love if the --verbose option could actually add that information. At the moment, unless I am doing something wrong, nx format:check --verbose has the same output as nx format:check.
Motivation
The command would give more information about what is actually wrong in the file format.
Suggested Implementation
I would love if the --verbose option could actually add that information.
Alternate Implementations
As an alternative, I would like even only to see either the line where the check fails, or maybe the broken rule.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:56
- Comments:31
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Itβs like a slap in the face without ever even telling you why. Imagine a compiler telling you βError, GFY, periodβ.
Please add this.
If it helps anyone, running
nx format:writesolved issue for me. Nevertheless, it would be nice if the --verbose flag provided some extra info.