Skip to content

Suggestion: Move languageOptions properties from nested parserOptions #891

@DMartens

Description

@DMartens

What problem do you want to solve?

Currently the playground generates a configuration which specifies sourceType in languageOptions.parserOptions instead of languageOptions. For example:

export default [
    {
        "languageOptions": {
            "parserOptions": {
                "ecmaFeatures": {
                    "jsx": true
                },
                "sourceType": "module"
            },
        }
    }
];

What do you think is the correct solution?

Move the properties languageOptions.parserOptions.{sourceType,ecmaVersion} to languageOptions.{sourceType,ecmaVersion}.

Participation

  • I am willing to submit a pull request for this change.

Additional comments

This change would be consistent with the documentation

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status

Implementing

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions