[cli]: Have a dedicated option to show up local environment information
See original GitHub issuePresent Scenario
Presently, the Issue template (Bug report) asks the user to provide a couple of information concerning his/her local environment.
What is intended?
IMO it would be good to have a dedicated option, preferably eslint --info
which would show up all the required information, and the Issue template could be updated accordingly.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Having a dedicated command to show up local environment ...
A dedicated info command would ease the workflow, and all the user has to do is to paste the results as shown. The...
Read more >Set up your local development environment
The best way to do this is to use a cross-platform tool based on Docker. This ensures the changes you make locally appear...
Read more >eb create - AWS Elastic Beanstalk
Use the EB CLI create command to create Elastic Beanstalk environments.
Read more >Developer CLI Operations - OpenShift Documentation
The developer CLI allows interaction with the various objects that are managed by OpenShift Dedicated. Many common oc operations are invoked using the ......
Read more >Command Line Options - Valve Developer Community
-forever, When you get to the end of the maplist, start over from ... -nocrashdialog, Stop some windows crash message boxes from showing...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In the TSC meeting two weeks ago, the TSC accepted this proposal with the implementation details to be figured out in this issue.
The consensus process mostly applies to new rules and rule enhancements, whereas this is a CLI feature, so I think we need the TSC to evaluate it.
I like the idea enough that I’ve added it to the TSC agenda for our next meeting.