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

Bug 107080

Summary:	Javascript editor should have formatting prefs similar to Java
Product:	z_Archived	Reporter:	Lev Epshteyn <levik>
Component:	Webtools.WST.Javascript	Assignee:	David Williams <david_williams>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	Keywords:	helpwanted
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Lev Epshteyn

2005-08-15 20:59:38 EDT

As Javascript is becoming more prevalent in web applications, the number of
people writing JS in corporate environments is growing. These developers are
often subject to pretty strict coding conventions. When developing Java, Eclipse
can help by allowing people specify formatting preferences in line with their
company standards, but the Javascript editor is woefully missing these features. 

I believe a lot of the preference available as far as code formatting in Java
should ultimately be duplicated by the JS editor, but at least the ommission of
having the option to have spaces be inserted for tabs seems very simple to correct.

Comment 1 Amy Wu

2005-08-16 09:48:01 EDT

To track the spaces for tabs issue in the JS editor, please CC yourself to Bug 
95618

Comment 2 Nils Hammar

2006-01-01 14:39:29 EST

In my opinion - is it possible to use the same formatter as for Java? The code style is basically the same for JavaScript, though some keywords are different.

This may actually apply to a wider scope of formatters that applies to languages with similar basic features like C, C++, Java and JavaScript.

Comment 3 David Williams

2007-12-17 01:59:18 EST

I'm doing a mass resolve of all open bugs in the wst.javascript component. 
Resolving to "won't fix". 

The reason is that the old wst.javascript component is being removed this release, and replaced by the wst.jsdt component. 

So ... if any owners of these wst.javascript bugs see the same problem in the wst.jsdt code, then please open a new bug on that component. 

Apologies we can't check each ourselves, but there's just too many (and too few people) so we'll need community help. Just glancing, I know for sure many will no longer be bugs but some may still be legitimate requests even in the new JSDT code.