jnmoal / go-guru Goto Github PK

Just wanted to inform you that both go-config and go-get have been consolidated into go-plus as of go-plus v5.0.0. See joefitzgerald/go-plus#503. This means that both go-get and go-config will be unpublished from atom soon so installing your package in atom will fail after that.

In order to fix this you have to change your code so that it will install go-plus instead of go-get and go-config (see package-deps in package.json). Beside that nothing else changes because go-plus provides the same services as go-get and go-config now do. (see PR #10)

Yet there is another opportunity for you: integrate go-guru into go-plus!

• it will be part of a way bigger community so everyone can benefit from your awesome package 😉
• more maintainers so we can share knowledge and issues could be fixed faster
• go-plus provides some other nice features like a built-in panel which you could use to display your results instead of having an additional panel.

This can either be done by you or if you want we (the maintainers of go-plus) can do this. There is already a simple integration of guru in go-plus anyway so this won't be a big deal.

/cc @joefitzgerald

[Enter steps to reproduce:]

1. ...
2. ...

Atom: 1.38.2 x64
Electron: 2.0.18
OS: Unknown Windows version
Thrown From: go-guru package 0.2.0

Stack Trace

Failed to activate the go-guru package

At Cannot find module 'atom-package-deps'

Error: Cannot find module 'atom-package-deps'
    at Module._resolveFilename (module.js:543:15)
    at Module._resolveFilename (~/AppData/Local/atom/app-1.38.2/resources/electron.asar/common/reset-search-paths.js:35:12)
    at Function.get_Module._resolveFilename (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:155156)
    at Module.require (/app.asar/static/index.js:53:43)
    at require (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:146462)
    at Object.activate (/packages/go-guru/lib/go-guru.js:12:5)
    at Package.activateNow (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:3539161)
    at measure (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:3538573)
    at Package.measure (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:3536204)
    at activationPromise.activationPromise.Promise (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:3538433)
    at new Promise (<anonymous>)
    at Package.activate (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:3538376)
    at PackageManager.activatePackage (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:381112)
    at config.transactAsync (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:380728)
    at Config.transactAsync (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:330844)
    at PackageManager.activatePackages (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:380678)
    at PackageManager.activate (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:11:380296)
    at t.loadState.then (~/AppData/Local/atom/app-1.38.2/resources/app/static/<embedded>:1:710821)
    at <anonymous>

Commands

Non-Core Packages

go-build 0.2.2 
go-debug 1.6.2 
go-guru 0.2.0 
go-outline 0.6.11 
go-plus 6.1.0 
go-signature-statusbar 1.2.3 
go-to-test 0.1.0 
scratch undefined 

Actually the scope is computed automatically by the guru package, but for the following reason:

• performance issue when the scope contains a lot of code
• possible wrong scope used (depending on project structure)

For those reasons, the go guru package shall present the scope to the user and let him alter it.

Escape does not work either, at least on linux.

This package shall display all the information returned by the guru describe command.

See the guru documentation for the returned information

• Type description
• Value description
• Package description

This package lacks of automated tests, at least to prevent any regression.

Add the "help wanted" flag because testing with javascript is new for me.

When I try to use "guru callers", I get guru: file code.go not found in loaded program.

Running it outside of atom works, but only if I specify a -scope.

Is there a way to specify a scope?

Actually the go-guru package activates when the user ask for the 'describe' mode.
Because of this, the functionnality is not working on the first call, the package doesn't display anything.

May be, this package should be activated when atom starts, or when a go file is open.