eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper
Javascript: Jump to declaration still not at JSDT's level
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 201
- Forks
- 76
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
Hi,
I've been stuck with Eclipse Luna for years now, because of it being (along with Mars) the last version where JSDT worked fine (syntax coloring unbroken).
Your tool seems finally to get close to JSDT in certain aspects, surpass it in others.
But really: the most useful feature in a tool like this (even more important than syntax coloring) is the Jump to declaration ! How can anyone work without it when the project becomes more and more complex ?
And WWD doesn't come close the JSDT regarding Jump to declaration. Or I'm missing something. It works in the same file, when there are prototype functions, but look at this example:
(function ()
{
var global = this || window;
var _Ctrls = null;
_Ctrls = global.Ctrls =
{
test: function()
{
//////
},
test2: function()
{
_Ctrl.test();
}
};
})
Typing F3 (Jump to declaration) on the test() call would give a message like "The operation is not applicable to the current selection etc..."
In JSDT it would take me to the test function declaration. It would even take me to it when called in another javascript file in the same project !
Can anyone tell if this a final behavior or is there a chance to fix it ?
Regards
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the supplied JavaScript example in Eclipse and invoke F3 on the test() call. Compare the behavior within one file and across JavaScript files in the same project with the JSDT behavior described. Done means Jump to declaration reaches the test function declaration instead of reporting that the operation is not applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100