Skip to content
This repository has been archived by the owner on Mar 23, 2024. It is now read-only.

Add requireEnhancedObjectLiterals #1985

Conversation

seanpdoyle
Copy link
Contributor

When { requireEnhancedObjectLiterals: true }, assert that all
object declarations use the new ES6 enhanced object literals.

@hzoo hzoo added this to the 2.6.0 milestone Nov 16, 2015
@seanpdoyle seanpdoyle force-pushed the sd-require-enhanced-object-literals branch from 7cde894 to eeae832 Compare November 16, 2015 16:07
When `{ requireEnhancedObjectLiterals: true }`, assert that all
object declarations use the new [ES6 enhanced object literals][babel].

[babel]: http://babeljs.io/docs/learn-es2015/#enhanced-object-literals
@seanpdoyle seanpdoyle force-pushed the sd-require-enhanced-object-literals branch from eeae832 to eda19c9 Compare November 16, 2015 16:13
@markelog markelog closed this in b8969d4 Nov 17, 2015
@seanpdoyle seanpdoyle deleted the sd-require-enhanced-object-literals branch November 17, 2015 13:40
@hzoo
Copy link
Member

hzoo commented Nov 19, 2015

We might want to think about splitting the rule into 2 separate rules later

@mmun
Copy link

mmun commented Dec 17, 2015

@hzoo Big 👍 to separating this into two rules. Is there a path to this? Perhaps requireEnhancedObjectLiterals: 'functions' | 'identifiers' | true? Additionally, it would be nice to disallow any combination as well. My use case is to disallow the identifier case, but require the function case.

@markelog
Copy link
Member

You are welcome to give a try :-), for both proposals

@mmun
Copy link

mmun commented Dec 18, 2015

Thanks for the green light.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants