Skip to content

feat: add esnext.string to ts libs #1013

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

Merged
merged 3 commits into from
Jul 21, 2021
Merged

feat: add esnext.string to ts libs #1013

merged 3 commits into from
Jul 21, 2021

Conversation

jake-bassett
Copy link
Contributor

Description

Added esnext.string to tsconfig libs.

@jake-bassett jake-bassett requested a review from a team as a code owner July 20, 2021 19:40
@codecov
Copy link

codecov bot commented Jul 20, 2021

Codecov Report

Merging #1013 (5dcb859) into main (ba2ed52) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1013   +/-   ##
=======================================
  Coverage   85.06%   85.06%           
=======================================
  Files         820      820           
  Lines       16863    16863           
  Branches     2190     2190           
=======================================
  Hits        14344    14344           
  Misses       2488     2488           
  Partials       31       31           

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 ba2ed52...5dcb859. Read the comment docs.

@github-actions

This comment has been minimized.

@@ -16,7 +16,7 @@
"noUnusedLocals": true,
"noUnusedParameters": true,
"downlevelIteration": true,
"lib": ["es2015", "es2016", "es2017", "esnext.array", "esnext.asynciterable", "dom"],
"lib": ["es2015", "es2016", "es2017", "esnext.string","esnext.array", "esnext.asynciterable", "dom"],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did you verify that we polyfill these?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not everything, but I tested replaceAll. What else should I look for?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we basically need to make sure that it works in any browser we support (not just local) - so either it's been implemented in all that we support, or safer - that core-js polyfills replaceall (I think that's all that comes in here, right?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, that I did check.

We are good on all modern browsers.

https://caniuse.com/?search=replaceAll

@jake-bassett jake-bassett requested a review from a team July 20, 2021 20:14
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@jake-bassett jake-bassett merged commit 68fbce5 into main Jul 21, 2021
@jake-bassett jake-bassett deleted the esnext-string branch July 21, 2021 00:13
@github-actions
Copy link

Unit Test Results

    4 files  ±0  262 suites  ±0   17m 22s ⏱️ +2s
945 tests ±0  945 ✔️ ±0  0 💤 ±0  0 ❌ ±0 
952 runs  ±0  952 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 68fbce5. ± Comparison against base commit ba2ed52.

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