Skip to content
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

Standardize the use of setter types #6708

Merged
merged 2 commits into from
Jun 15, 2020
Merged

Standardize the use of setter types #6708

merged 2 commits into from
Jun 15, 2020

Conversation

bigtimebuddy
Copy link
Member

The newer version of ESLint and TypeScript plugins enforce this rule by default. This is a preemptive change so that we can support the latest tools. Adds setter types where they were missing from the code.

@codecov-commenter
Copy link

codecov-commenter commented Jun 15, 2020

Codecov Report

Merging #6708 into dev will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##               dev     #6708   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           15        15           
  Lines          671       671           
=========================================
  Hits           671       671           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 04915ea...198800f. Read the comment docs.

@bigtimebuddy bigtimebuddy added the ✅ Ready To Merge Helpful when issues are in the queue waiting to get merged. This means the PR is completed and has t label Jun 15, 2020
@bigtimebuddy bigtimebuddy merged commit 5028949 into dev Jun 15, 2020
@bigtimebuddy bigtimebuddy deleted the dev-setter-types branch June 15, 2020 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✅ Ready To Merge Helpful when issues are in the queue waiting to get merged. This means the PR is completed and has t
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants