-
Notifications
You must be signed in to change notification settings - Fork 628
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
javascript: Got "ctags: Warning: ignoring null tag" #900
Comments
Is there any update on this? Or am I doing something wrong? The code I'm trying to tag is Javascript/React :) |
Apparently it is related to Object destructuring like: const { name, email } = user; |
I have not inspected the warning well.
|
Not sure if I got your question but the specification for the Object Destructuring is on the ECMAScript specification: :) |
Thanks. That is what I need. |
Why does this issue not be addressed? I've got the same problem. |
how did you remove the warning? |
I didn't remove the warning. |
well, I've got the same issue, |
Looks like no one is going to fix this issue |
For the destructural binding, I tried once.
The branch introduces so many changes. |
In this case, ctags says nothing.
In this case, I got a warning. This will be an important hint fix for the original input. |
I've tried it, a very good solution, thanks. |
Hi Although this is not contributing to the issue in ctags itself, I created a Just in case you frequently run ctags on the command line and want to hide the warnings until the issue is fixed. Dietrich |
I also get this warning with array destructuring : |
@Strangehill, could you add the same comment to #1112? |
of course |
Thank you. |
Related to universal-ctags#900, universal-ctags#1112, and universal-ctags#3427. When the parser tries making a tag with empty name, an assertion in registerEntry fails. The parser side should be fixed but it will take a time. This change puts guard conditions around registerEntry to avoid the failures. THIS IS A TEMPORARILY SOLUTION. Signed-off-by: Masatake YAMATO <[email protected]>
That does not shut it up on my side, at all 🤷 I'll have to go with @dietrichm alternative for the time being as I'm heavily using deconstruction which ctags really spammy. |
Could you try #3435? |
I'm moving to the PR. Let me know if you want to keep it here. |
The text was updated successfully, but these errors were encountered: