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

Bug: Neogen not functioning in vue files. #169

Open
TheMartonfi opened this issue Apr 16, 2024 · 4 comments · May be fixed by #212
Open

Bug: Neogen not functioning in vue files. #169

TheMartonfi opened this issue Apr 16, 2024 · 4 comments · May be fixed by #212

Comments

@TheMartonfi
Copy link

I'm currently trying to configure neogen to generate jsdoc comments for a vue project, I've tested that neogen works fine in js, ts, jsx, tsx so the plugin does work fine for those file types.

When attempting to run ':Neogen' nothing happens in vue files. If there's any way to debug this further please let me know as I'm now at a lost as to why the plugin isn't working.

@charnley
Copy link

Similarly. I tried to enable jsdoc for Svelte (the same way as Vue), but nothing happened.

@charnley
Copy link

After debugging the neogen lua with some vim.print statements, it looks like the mixed language files has problems finding the right javascript node from the tree. I am not a treesitter expert though, but the locator returns nill when trying to find any of the types like function.

target_node = get_node(all_types_map[filetype]) -- return nill

I think vue might have the same issue because of the HTML-like file format, as svelte.

@Rahlir
Copy link

Rahlir commented Feb 25, 2025

Any update on this? Neogen doesn't work in Vue for me either.

@Rahlir
Copy link

Rahlir commented Mar 6, 2025

Any update on this? Neogen doesn't work in Vue for me either.

Well, when I was updating my luasnip config, I noticed that my tree-sitter conditions also don't work for vue. After some digging around, I found out that this is because neovim by default ignores injected languages. So, the fix for this issue is actually trivial. I submitted a PR for this in #212.

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

Successfully merging a pull request may close this issue.

3 participants