Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 444998 - Ability to group properties within a setting
Summary: Ability to group properties within a setting
Status: RESOLVED WORKSFORME
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 6.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mark Macdonald CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 436086
  Show dependency tree
 
Reported: 2014-09-24 12:52 EDT by Mark Macdonald CLA
Modified: 2015-12-03 12:03 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Macdonald CLA 2014-09-24 12:52:29 EDT 
The list of JS validator settings has grown too large. It needs to be partitioned into sub-categories.

In order to do this, the orion.core.setting extension point needs to support additional field(s) to slot the setting's properties into a sub-category at display time.
Comment 1 Curtis Windatt CLA 2014-09-24 13:02:54 EDT 
While JS is the only one needing the granularity currently, other languages may want something similar in the future.  It would be nice for the category names to match across languages (where appropriate).
Comment 2 Mark Macdonald CLA 2014-09-26 17:10:13 EDT 
(In reply to Curtis Windatt from comment #1)
> While JS is the only one needing the granularity currently, other languages
> may want something similar in the future.  It would be nice for the category
> names to match across languages (where appropriate).

I believe someone suggested dividing up the JS rules using the categories here: 
https://github.com/eslint/eslint/tree/master/docs/rules

A few of them are js-specific but others ("Possible Errors", "Stylistic Issues" etc) are general enough to reuse
Comment 3 John Arthorne CLA 2015-05-05 16:30:29 EDT 
This open bug report had a target milestone in the past. The target milestone has been removed. Please target for a date in the future or leave the target blank if it is not known.
Comment 4 Curtis Windatt CLA 2015-12-03 12:03:21 EST 
We are already using the same categories as ESLint under the Javascript Validation settings page.  Closing as WORKSFORME.