Skip to content
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

command 'extension.snipsnap_activate' not found #17

Open
abosnjakovic opened this issue Jul 9, 2020 · 6 comments
Open

command 'extension.snipsnap_activate' not found #17

abosnjakovic opened this issue Jul 9, 2020 · 6 comments

Comments

@abosnjakovic
Copy link

Installed the extension on Popos 20.04, vs code installed via flatpak.

Opening command pallet > Snipsnap: Fetch the snippets results in;
Command 'Snipsnap: Fetch the snippets' resulted in an error (command 'extension.snipsnap_activate' not found)

Let me know of other information you may require to help diagnose this one.

@mmoga
Copy link

mmoga commented Jul 23, 2020

I'm experiencing the same issue. VS Code v1.14.2

@bolotskydev
Copy link

Currently there is only one activation event that triggers this ext: workspace should contain package.json. Can you confirm that your workspace indeed contains package.json, but still nothing is working? 🤔

@mmoga
Copy link

mmoga commented Jul 26, 2020

@bolotskydev Thanks for getting back to me. I created a new project (and it has a package.json) and it's working as expected. Sorry for the waste of time. 😞

@abosnjakovic
Copy link
Author

@bolotskydev Yes, in fact it contains multiples. Maybe that's the problem, creating a project with just on package.json in the root works fine. A mono-repo with many does not. Even a mono-repo with one package.json that it not in the root does not work.

@paragbaxi
Copy link

building microservices app which requires a package.json file per service. would be good if this could support multiple package.json. i would expect that snipsnap would use the package.json file from the closest parent directory relative to the file that it was triggered on.

@akd-io
Copy link

akd-io commented Oct 16, 2020

Fetching is also not working for me in a workspace with a single folder containing the project including package.json.
Would indeed be very nice with multiple package.json support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants