Stuck on an issue?

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.

Issue Description

A lot of things have moved recently, and the project has had several major refactors since the beginning. As such, the code could be much cleaner. Once more tests are added and we can ensure large changes don’t lead to regressions, I’d like to do the following things:

  • Find a general convention for defining variables (making wrappers around registerCommand or utility functions called from several registerCommands).
  • Better name commands, with more descriptive categories and a more obvious mapping between command name and source file name in src/commands.ts.
  • Clean up extension.ts.
  • Reorder imports in all files.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

yuchenshicommented, Jun 22, 2020

@71 How do you feel about cutting a release after #101 is merged? I think we’ve got the most low-hanging fruits and we can get more help to find more edge cases if a new version is released.

Also, FYI I imagine objects in caret-based selections is the largest source of bugs. There are tons of edge cases and we don’t have great coverage. I’ve written extensive tests for character-based and used it manually for a while, but not carets. We can also put that in known issues and call for help.

71commented, Jun 15, 2020

@tshort We were planning on releasing the update on the marketplace but ended up working on other things for a while. Now we’re trying to fix issues that won’t be too much work and release that on the marketplace, since there haven’t been too many issues with master.

And glad to know you like it! I’ve been running it daily without issues for a few weeks, but since I’m not a power user myself either, I was worried there would be issues in the parts I rarely use.

Read more comments on GitHub >

github_iconTop Results From Across the Web

What is Code Health? How do you measure it? - CodeScene
The Code Health scale goes from 10 (healthy code that's relatively easy to understand and evolve) down to 1, which indicates code with...
Read more >
CodeHealth - An Educational Community to Share, Teach ...
CodeHealth is an educational community where medical professionals can learn, share and teach each other the science and art of medicine.
Read more >
Code Health: Google's Internal Code Quality Efforts
What the Code Health group does is work on efforts that universally improve the lives of engineers and their ability to write products...
Read more >
Code Health - MediaWiki
In short, Code Health is about the maintainability, readability, stability, and simplicity of code. Although there have been many efforts in ...
Read more >
Improve Code Health - Sourcegraph
Engineering teams need to track and measure code quality consistently to monitor code health across their entire codebase, but current tools don't make...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found