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: redux connect memo issue related to spec upserting #564

Merged
merged 1 commit into from
Feb 21, 2020

Conversation

nickofthyme
Copy link
Collaborator

Backports the following commits to 17.1.x:

@codecov-io
Copy link

codecov-io commented Feb 21, 2020

Codecov Report

❗ No coverage uploaded for pull request base (17.1.x@0479ba7). Click here to learn what that means.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff            @@
##             17.1.x     #564   +/-   ##
=========================================
  Coverage          ?   71.42%           
=========================================
  Files             ?      208           
  Lines             ?     6114           
  Branches          ?     1175           
=========================================
  Hits              ?     4367           
  Misses            ?     1730           
  Partials          ?       17
Impacted Files Coverage Δ
src/state/spec_factory.ts 92.3% <100%> (ø)

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 0479ba7...c97d8c1. Read the comment docs.

@nickofthyme nickofthyme changed the title [17.1.x] fix: redux connect memo issue related to spec upserting (#563) fix: redux connect memo issue related to spec upserting Feb 21, 2020
@nickofthyme nickofthyme merged this pull request into elastic:17.1.x Feb 21, 2020
@nickofthyme nickofthyme deleted the backport/17.1.x/pr-563 branch February 21, 2020 05:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants