Skip to content

Use new eslint config for es6 / goog.module #5160

@maribethb

Description

@maribethb

Describe the solution you'd like

After the round of goog.module conversion is finished, and we've converted all of the vars to let/consts, and clang-formatted all the things... we need to update the eslint config. We can't do it beforehand, because all of the unconverted code will have a lot of errors. Afterwards, there will probably still be some errors that we need to fix to actually be in agreement with the Google style guide.

Ideally, we'd be able to use the same library that we use in blockly-samples that understands the Google style guide: https://github.com/google/eslint-config-google. I think this is feasible, and while we will have some real problems to clean up afterwards, we'd be
a) conforming to Google style
b) using the same style in both blockly and blockly-samples.

Describe alternatives you've considered

We might be able to use the same eslint config as blockly-samples, or extend that config (as opposed to both extending from the same config, but not each other). I'm not sure how feasible this will be yet, so when we're making this change, we should consider how similar they are and if this makes sense.

Metadata

Metadata

Labels

issue: feature requestDescribes a new feature and why it should be added

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions