-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: should download latest release on install #68
Conversation
268e722
to
7fbfec2
Compare
@pjlast / @mrnugget could you give this a go? I think this is ready to go. You should be able to wipe out your If so, I'll merge, then do a version bump and no more build step for users :) just a quick download step. |
First time user trying out this branch - this might not be strictly related to this branch but I'm having issues with initial start up. Stack trace
This is pre setting up sourcegraph login/auth via |
@tjdevries works! I just wiped everything from disk, added plugin, The only thing that confused me: I think I have to restart Vim after the installation for the |
@jamestrew I pushed a new version of this, which should prevent the errors from happening. Also though, it's |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there's something sus happening around
Lines 118 to 121 in 6138d65
local cody_data = data.get_cody_data() | |
cody_data.token = data.token | |
cody_data.endpoint = data.endpoint | |
data.write_cody_data(cody_data) |
I don't think the auth data is actually being saved correctly. So even though the SourcegraphLogin
command shows up for me now (typo in my earlier comment), I still get caught on require("sg.request").request
.
If I set up env variables for SRC_ENDPOINT
, SRC_ACCESS_TOKEN
, things look good though.
I do get some logging happening in the command line, but I take it that's just part of the pre-release nature of this plugin.
@@ -1,6 +1,10 @@ | |||
---@tag sg.rpc | |||
---@config { ["module"] = "sg.rpc" } | |||
|
|||
if not require "sg.request" then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like with no login/auth, require "sg.request"
is literally true
so this condition will pass and still lead to the bad attribute access on line 8.
@jamestrew check last commit... haha i figured it out |
No description provided.