New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump Style Rules and Linting #2084
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AdrianAndersen
requested review from
odinuge,
LudvigHz,
erlingfn,
JonasBak,
SmithPeder and
theodorsm
December 30, 2020 21:24
odinuge
reviewed
Jan 1, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Just a few nits, otherwise goood to go!
(Splitting of commits was awesome!)
AdrianAndersen
force-pushed
the
bumpStyleAndLinting
branch
from
January 1, 2021 15:41
b82e205
to
af9da18
Compare
AdrianAndersen
force-pushed
the
bumpStyleAndLinting
branch
from
January 2, 2021 16:14
af9da18
to
741107e
Compare
odinuge
approved these changes
Jan 4, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog
default:
-tag (ez fix)allowed.hasOwnProperty(key)
=>Object.prototype.hasOwnProperty.call(allowed, key)
(improves secuirty)map()
were unused needed to be moved toforEach()
location
andconfirm()
are restricted globals, and had to be moved towindow.location
andConfirmModalWithParent
() => (func1(), func2())
syntax, which had to be rewritten. I am a bit unsure about these rewrites, since I don't fully understand the aforementioned syntax. Hopefully someone can check that these are correct 🙂useCallback()
, passed [] to fix eslint warningRevert PR With Previous Review Threads
Future changes
As I worked on bumping and configuring eslint, I discovered that we have a quite poorly configured .eslintrc. There are many eslint plugins currently not in use, which limits eslint's benefits. In a future PR, I will configure some sane defaults for eslint, as well as enable default rules for the plugins we currently don't use. This will help improving the code quality of our codebase.