672823 - GCLI needs to provide completion hints for Javascript to match the JSTerms hints

Status: RESOLVED FIXED

(DevTools :: General, defect)

Comment 1

[Kevin Dangoor]

Just making a note that depending on how things are implemented, we might want this bug to fix bug 672733

Comment 2

[Joe Walker [:jwalker]]

Good spot, thanks.

Comment 3

[Joe Walker [:jwalker]]

Mihai is doing e10s work on the JS completion. I hope we can use this as the basis for JS completion in GCLI.
Ideally the e10s work would extract the completion logic into a separate JSM with a well defined API, which should help us re-use it in a CommonJS module.

CCing Mihai.

Comment 4

[Mihai Sucan [:msucan]]

There's e10s work underway that allows marshaling of objects and their properties for the Property Panel, in bug 673148.

That work is very much reusable for the existing autocomplete code and for the upcoming GCLI autocomplete work that needs to be done.

Once I get back to work on the e10s patch in 673148 I will implement a sort of GC for the evaluated content objects, and I will also move to making the existing autocomplete code work with the new e10s-friendly API.

Once that's done I believe you can do the work needed here. (if it is desired that this bug is fixed in an e10s friendly approach from the start.)

Comment 5

[Joe Walker [:jwalker]]

Marking as minotaur, and adding estimates

Comment 6

[Joe Walker [:jwalker]]

Should add - the estimates are guestimates.