Search Results for "code analysis"

ESLint plugin for Vue.js. This plugin allows us to check the template and script of .vue files with ESLint, as well as Vue code in .js files. This plugin supports the basic syntax of Vue.js 3.2, script setup, and CSS variable injection, but the ref sugar, an experimental feature of Vue.js 3.2, is not yet supported. If you have issues with these, please also refer to the FAQ. If you can't find a solution, search for the issue and if the issue doesn't exist, open a new issue. Be aware that...

Similar to indent-blankline, this plugin can highlight the indent line, and highlight the code chunk according to the current cursor position. Using profile.nvim for performance analysis, all experiments were conducted on macOS with alacrity, Neovim window height was 66 lines, and the code file was typescript.js, starting from the first line to the five hundredth line. The average rendering time per render was 0.7ms.

...Look up documentation with :GoDoc or :GoDocBrowser, easily import packages via :GoImport, remove them via :GoDrop. Precise type-safe renaming of identifiers with :GoRename. See which code is covered by tests with :GoCoverage. Add or remove tags on struct fields with :GoAddTags and :GoRemoveTags. Call golangci-lint with :GoMetaLinter to invoke all possible linters (golint, vet, errcheck, deadcode, etc.) and put the result in the quickfix or location list. Lint your code with :GoLint, run your code through :GoVet to catch static errors, or make sure errors are checked with :GoErrCheck. ...

...Very simple to use: just set an environment variable (command line) or switch on a radio button (web request) to profile your script. Thus, you are free of manually instrumenting your code (Ctrl-C a long running command line script is even supported). Using a dedicated browser extension or command line launcher. Multi metrics capable: 22 are currently supported (various time & memory metrics, included files, objects in use, I/O...). Able to collect data without losing context. For example Xhprof (and potentially its forks) aggregates data per caller / callee pairs, which implies the loss of the full call stack and forbids timeline or Flamegraph based analysis.