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

fix: compatibility with named export and es5 #1314

Merged
merged 1 commit into from
May 20, 2021

Conversation

cap-Bernardito
Copy link
Member

This PR contains a:

  • bugfix
  • new feature
  • code refactor
  • test update
  • typo fix
  • metadata update

Motivation / Use-Case

fixed compatibility with named export and es5

Breaking Changes

No

Additional Info

No

@codecov
Copy link

codecov bot commented May 20, 2021

Codecov Report

Merging #1314 (bc3abc9) into master (8f1a6fc) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1314   +/-   ##
=======================================
  Coverage   98.30%   98.30%           
=======================================
  Files          11       11           
  Lines         885      885           
  Branches      296      296           
=======================================
  Hits          870      870           
  Misses         12       12           
  Partials        3        3           
Impacted Files Coverage Δ
src/utils.js 97.42% <100.00%> (ø)

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 8f1a6fc...bc3abc9. Read the comment docs.

@alexander-akait alexander-akait merged commit 0cf8cde into master May 20, 2021
@alexander-akait alexander-akait deleted the fix-compatibility-es5 branch May 20, 2021 12:41
This was referenced Sep 15, 2024
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