Closed tgriesser closed 7 years ago
I'm very interested in adding support for this but it will require quite a refactoring
Hi sorry for the delay, this project is now deprecated in favour of flow-runtime which aims for full flow compatibility. flow-runtime has much better error messages and will tell you precisely which properties fail and why.
Thanks for the library!
I'd really like to see a way to know what specific missing or invalid property triggers an error, and the object it occurred on. If you have an array of typed objects, or a lot of properties on an object, and a key on one of those objects missing, the generic error isn't super helpful or obvious:
(this goes on for several hundred lines)
I'd rather see the type signature of just the failing object, and then the actual value of object which caused it to fail. If this is something you'd consider adding, I'd be willing to take a shot at implementing.