JSDT/Confcalls/Minutes 20160223

Logistics

See JSDT/Confcalls

Attendees

Dennis, Alexey, Gorkem,Patrik,Orlando,Ilya,Victor,Chuck,Alina,Adalberto,Victor,Sosa

Notes

• JSON Editor:
  • Patrik had no time to look into this
  • Chuck: Tests are not showing lack of sync
  • Alina: working on synch issue, mainly focused inIJSONModel.
  • Chuck (or Victor) is opening a CQ for including the tests from original contribution
  • Victor has a workaround, that cannot be used as final solution but can help others to continue working.
    • https://github.com/vrubezhny/webtools.sourceediting/tree/bug486860
    • (Avoid CCE and helps with contentassist)
  • ContentAssist
  • Alexey has provided a fix. https://git.eclipse.org/r/#/c/66775/
  • We could use the current fix, without throwing no exceptions.
  • this is not a priority item we should proceed with things with higher priority and disable completely

• Debugger
  • Dennis did Knowledge Transfer, and worked with Ilya. They had a solution to be submitted to improve debugger
  • Ilya started working on breakpoint translation, seems a vast issue,
  • Gorkem: we can reduce by considering minimum use cas which is putting a breakpoint through normal Javascript editor
  • Dennis: for now you should be able to put breakpoints with normal JSDT editor, and then you should be able to stop on breakpoint.
  • Orlando and Adalberto are looking into the debugger:
    • https://bugs.eclipse.org/bugs/show_bug.cgi?id=359436
    • https://bugs.eclipse.org/bugs/show_bug.cgi?id=484597

• Gulp / Grunt / NPM
  • They are ready to test, and we should assign a testing task to someone
  • Ilya has the latest change at https://git.eclipse.org/r/#/c/67148/
  • Ilya: we need a QA guy to test Bower/Gulp/Grunt for 5 hours per week
  • Gorkem will arrange Red Hat testing time.

• Parser
  • Gorkem: Esprima based parser is integrated plus AST is created. So we can integrate with IDE features, code is on GitHub.
  • The only part we're using the old parser is the validation to validate the syntax errors, but at a some point we'll use the validator being impl by Orlando
  • In Orion they're using Esprima + ESLint, we could consider.
  • Shane is implementing ES6 highlighting and ES level configuration on projects is a problem , as all projects are ES3 level
  • Gorkem: seems we should drop support for ES levels, as after ES3 there is no continuity. As example ES4 support is not complete/active
  • Victor: it is likely we have to drop them, after all editors are synced to the highest ESx level (ES6)
  • Gorkem we can drop. The trend seems to be using TransPilers
  • Chuck: seems this is the right way
  • Victor: the rationale is the existing users are not giving importance to the EcmaScript level

• V2 Validator
  • Orlando is working on this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=482841 and he has requested feedback for his change on Gerrit: https://git.eclipse.org/r/#/c/64672/, which actually waited with no response for several days.
  • Gorkem just replied this morning and seems this is the right track. Validator code initial proposal is good now, so the next step is to make the current JavaScript builder to invoke the new V2 validator.
  • After this, the compiler structure will need to switch to the new Esprima parser/validator instead using the old Compiler one.

• Code Completion
  • Ian is making progress with code completion with object literals, in two ways: suggesting IES6 keyworsd, and variable & functions.
  • Victor: we coud consider templates based code-completion.
  • Gorkem: we're not making any change in templates completion

• Docs:
  • Patrik
    • link to a transcript about debugger: http://ether-man.rhcloud.com/p/debugger_call
    • making a video on how to setup JSDT