Skip to content

Add eslint#99

Draft
karlbecker wants to merge 3 commits intodevelopfrom
feature/add-eslint
Draft

Add eslint#99
karlbecker wants to merge 3 commits intodevelopfrom
feature/add-eslint

Conversation

@karlbecker
Copy link
Copy Markdown
Member

Summary - BZ-XXXX

Adds eslint to this repo to potentially reduce the chance of undesired behavior sneaking in

Description

This is just a draft for now, but wanted to get your opinion on adding eslint to the repo. Do you like this setup so far @tiandavis ?

I didn't address all the eslint warnings and errors. Instead I just took care of the majority of them by adding a few globals and specifying a couple of values in env

No need to look at this while you're finishing up the Summon 2021 changes - this is all for merging after we get those changes out. But since I was just in here I wanted to give a quick crack at this.

Let me know what you think sometime after Summon 2021 is ready for review - thanks!

Also: think we want to add a package-lock.json file to this repo?

Deploy Precautions

  • None

Whoa, we don't have package-lock in this repo? Do we want to?
CI build should now fail
@karlbecker karlbecker self-assigned this Dec 9, 2021
@tiandavis
Copy link
Copy Markdown
Contributor

Adding the package-lock.json sounds good @karlbecker! I've learned my lesson with React breaking because a downstream package broke ALL THE THINGS. 👍

IIRC, there was some issue with const and let because of the operating environment. I wonder if there is a rule we can create for eslint to stop the build if those are added. Until we can use a build system with babel, we still have to validate the es6 functions we choose have good cross browser compatibility, but not sure if this is something eslint can help us with.

Thank for getting this going! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants