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.
Why do all formatting errors have code IDE0055?
See original GitHub issueThe .editorconfig formatting rules allow quite a varied (and increasing) number of configuration options as to exactly how code should be formatted. It seems quite likely that one would want to have different warning levels for the various different formatting issues, and sometimes want to outright suppress some by setting their severity to ‘none’. However this can’t be done as long as they all throw up the code IDE0055. Why not have different error codes for the different formatting issues to allow more fine-grained control?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:17 (8 by maintainers)
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
If you’re signaling an error, you must know what caused the signaling, no? You would know which constraint was crossed?
@marcospgp Can you file a new issue for this? It’s unrelated to the current issue, which is no longer being updated.