4 ms·
I think that the best editing experience would be editor combined with debugger. JavaScript is a dynamic language, a lot of autocompletes before run is just gue
by vbezhenar 9y ago
I think that the best editing experience would be editor combined with debugger. JavaScript is a dynamic language, a lot of autocompletes before run is just guesses. But if you're running program and stopped it at that line, you know all available objects and their properties, so autocomplete would be perfect. It would require a bit different development style, but it might worth it.
- DougBTX 9y agoChrome's development tools actually allow saving changes to the JS files AFAIK, or going the other way around, it is possible to debug JS running in the browser from VS Code using the devtools-protocol: https://github.com/ChromeDevTools/devtools-protocol https://github.com/ChromeDevTools/devtools-protocol
- chatmasta 9y agoProblem is enumerating all the possible code paths that could break at the current line.
- seanmcdirmid 9y agoIf you just want a heuristic, having one value is really useful. Polymorphism is rather rarely used anyways.
- vbezhenar 9y agoThat's developer problem. I'll provide input values for needed use-case myself (for example with unit test or just manually) and IDE should stop at given line and provide autocomplete. I don't think that there's implementation difficulty, it's just a bit different style of coding, but it should work very well with test driven development.