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

Simplify slightly logic around keeping latest value in ref #513

Merged
merged 1 commit into from
Jun 4, 2019

Conversation

Andarist
Copy link
Contributor

@Andarist Andarist commented Jun 3, 2019

No description provided.

@@ -0,0 +1,12 @@
// @flow
Copy link
Contributor Author

@Andarist Andarist Jun 3, 2019

Choose a reason for hiding this comment

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

I would gladly just install mine - https://github.com/Andarist/use-latest but got an impression that u dont like external deps here 😉

@codecov
Copy link

codecov bot commented Jun 3, 2019

Codecov Report

Merging #513 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #513   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          14     15    +1     
  Lines         231    231           
  Branches       57     56    -1     
=====================================
  Hits          231    231
Impacted Files Coverage Δ
src/ReactFinalForm.js 100% <100%> (ø) ⬆️
src/useField.js 100% <100%> (ø) ⬆️
src/useLatest.js 100% <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 e411e15...37ed178. Read the comment docs.

@erikras erikras merged commit fd32073 into final-form:master Jun 4, 2019
@erikras
Copy link
Member

erikras commented Jun 11, 2019

Published in v6.1.0.

@lock
Copy link

lock bot commented Jul 11, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants