Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 426746

Summary:	Should `console` be added to builtins?
Product:	[ECD] Orion	Reporter:	Mark Macdonald <mamacdon>
Component:	JS Tools	Assignee:	Project Inbox <orion.client-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public, ken_walker
Version:	5.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Mark Macdonald

2014-01-27 15:31:27 EST

Currently you need the flag /*jslint browser:true*/ or /*jslint node:true*/ in your file in order to get method completions for the "console" global variable (console.log(), console.warn() etc)

This is unfortunate since the console methods are available in many environments. Although console is not a real built-in according to the ECMA spec, we should consider treating it as a builtin for content assist.

Comment 1 Curtis Windatt

2014-01-27 15:54:44 EST

+1
amd:true also adds the console completions.

Comment 2 Ken Walker

2014-01-27 15:57:43 EST

+1

Comment 3 Mark Macdonald

2015-05-04 11:35:15 EDT

Now the 'console' error provides a Quick Fix that will set your /*eslint-env */, which fixes the error. I am happy with the current state, reopen if you disagree.