Skip to content
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.

Do not fail if no export is found #212

Closed
KnisterPeter opened this issue Nov 1, 2016 · 0 comments · Fixed by #213
Closed

Do not fail if no export is found #212

KnisterPeter opened this issue Nov 1, 2016 · 0 comments · Fixed by #213
Assignees
@KnisterPeter
Labels
bug

Comments

@KnisterPeter
Copy link
Owner

This is a bug (breaking change) from 0.11/0.12/0.13.
It should be possible to provide a file without react classes or propType definitions without failure.
@KnisterPeter KnisterPeter self-assigned this Nov 1, 2016
KnisterPeter added a commit that referenced this issue Nov 1, 2016
@KnisterPeter
fix: allow empty or non-export input files
b33049a 
This fixes the behaviour of throwing if no export or propType definition was found in the given
file. This reverts the error behaviour to the state of 0.13

FIX #212
@KnisterPeter KnisterPeter mentioned this issue Nov 1, 2016
Merged
KnisterPeter added a commit that referenced this issue Nov 1, 2016
@KnisterPeter
fix: allow empty or non-export input files (#213)
1dca59c 
This fixes the behaviour of throwing if no export or propType definition was found in the given
file. This reverts the error behaviour to the state of 0.13

FIX #212
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@KnisterPeter KnisterPeter

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: allow empty or non-export input files KnisterPeter/react-to-typescript-definitions
1 participant
@KnisterPeter