A software developer by profession. I Have 2+ years of experience in writing code and building systems. Pretty good in Golang. My free time includes working on pet projects and making myself better.
A software developer by profession. I Have 2+ years of experience in writing code and building systems. Pretty good in Golang. My free time includes working on pet projects and making myself better.
Yes, it goes to same page but different package documentation. Imagine you are researching something and come across multiple repositories. Will you bookmark all them?
If I really need them, yes. (Generally I will have one link and do searches from this one, I will have other bookmarks of the same site if I go regularly on particular pages)
As I understand your extension, when you click on your extension button and you are on a golang repo, you are redirected to the related documentation. When I'm working on a project, I not going to check their github repo, I'm directly on their doc. That's why I'm not understanding the usage.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't understand the use case here. Do you mean having a favourite link to pkg.dev and modify it every time you want to see the documentation?
No, just have the link in your favorite bar. (When you check the little star to bookmark the link)
The plugin seems to always go to the same page
Yes, it goes to same page but different package documentation. Imagine you are researching something and come across multiple repositories. Will you bookmark all them?
If I really need them, yes. (Generally I will have one link and do searches from this one, I will have other bookmarks of the same site if I go regularly on particular pages)
As I understand your extension, when you click on your extension button and you are on a golang repo, you are redirected to the related documentation. When I'm working on a project, I not going to check their github repo, I'm directly on their doc. That's why I'm not understanding the usage.