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

Add simple test for generic FieldRenderProps type #439

Merged

Conversation

Andarist
Copy link
Contributor

@Andarist Andarist commented Mar 6, 2019

No description provided.

@codecov
Copy link

codecov bot commented Mar 6, 2019

Codecov Report

Merging #439 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #439   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          15     10    -5     
  Lines         235    210   -25     
  Branches       58     62    +4     
=====================================
- Hits          235    210   -25
Impacted Files Coverage Δ
src/FormSpy.js 100% <0%> (ø) ⬆️
src/ReactFinalForm.js 100% <0%> (ø) ⬆️
src/Field.js 100% <0%> (ø) ⬆️
src/useField.js
src/useFormState.js
src/useForm.js
src/useConstant.js
src/useWhenValueChanges.js
src/flattenSubscription.js
src/testUtils.js
... and 2 more

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 7315a3a...9c5cdad. Read the comment docs.

@erikras
Copy link
Member

erikras commented Mar 6, 2019

This pull request introduces 2 alerts when merging 1e1d5fe into a3ca5f1 - view on LGTM.com

new alerts:

  • 2 for Unused variable, import, function or class

Comment posted by LGTM.com

@Andarist Andarist force-pushed the ts-test/generic-field-render-props branch from 1e1d5fe to 0697fd6 Compare March 6, 2019 17:54
@erikras
Copy link
Member

erikras commented Mar 6, 2019

This pull request introduces 2 alerts when merging 0697fd6 into a3ca5f1 - view on LGTM.com

new alerts:

  • 2 for Unused variable, import, function or class

Comment posted by LGTM.com

@erikras
Copy link
Member

erikras commented Apr 9, 2019

Can't ts-essentials be a dev dependency?

@Andarist
Copy link
Contributor Author

Andarist commented Apr 9, 2019

Not rly, because the imported thing would have to be inlined during build, but .d.ts files are distributed as is (building them anyhow when the source is not authored in TS would be a huge overkill).

We could inline manually this implementation, but personally I find it counter-productive.

@erikras
Copy link
Member

erikras commented Apr 9, 2019

I'm correct in assuming that we could add a hundred different type helper libs as dependencies, and it would have no effect whatsoever on the final bundle size the browser sees, because TS is entirely build-time, right?

@vladshcherbin
Copy link

vladshcherbin commented Apr 9, 2019

@erikras I believe this is partly correct, adding TS packages to dependencies will install unnecessary packages for devs who are not using TS (types won't be bundled in browser build though).

This is what I found out when tried to add types to one of my packages. For js projects, adding types to @types repo is a much better solution and is recommended in TS docs.

@erikras erikras merged commit 9cd64b5 into final-form:master May 24, 2019
@erikras
Copy link
Member

erikras commented May 24, 2019

This pull request introduces 2 alerts when merging 9c5cdad into 7315a3a - view on LGTM.com

new alerts:

  • 2 for Unused variable, import, function or class

Comment posted by LGTM.com

@erikras
Copy link
Member

erikras commented May 24, 2019

Published in v5.1.1.

@Andarist Andarist deleted the ts-test/generic-field-render-props branch May 25, 2019 07:05
@lock
Copy link

lock bot commented Jun 24, 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 Jun 24, 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

3 participants