Commit activity
Last 12 weeks · 0 commits
Community health
4 of 6 standards met
Recent PRs & issues
Will this library continue to support PropTypes validation? If yes, in which way? I'm asking because I don't plan to move to TypeScript, so my only option for now is to write a custom babel-plugin which will call .
We got this error from airbnb proptypes... haven't faced such issue before. it throws an error on line For more detail can check here for issue that we catch on our sentry instance: https://umai.sentry.io/share/issue/23296973e27047f28f20447e8519fcc4/ Versions:
Recent fixes
All the other prop types checks we use both from airbnb and elsewhere seem to work as expected, but has no effect no matter where we try it or what we pass it. We're using with . Any thoughts? Is it broken? Surely we can't be the only ones? We do not use Use of airbnb-js-shims, but after reviewing the shims, all functions are already supported in our environment without shimming.
Things that work as expected: breaks for anything that is not , including . breaks on breaks on Things that do not work as expected: breaks on passes on
I've expanded the helper to include children of fragments. This resolves #71, which means that the validator can now validate the type of children within fragments. I have added tests for this validator; the tests are copied from the similar tests for children passed an array. This also affects and validators which both use the helper. I have not added the tests for these, but I can if necessary.
Repository: ljharb/prop-types-tools. Description: Custom React PropType validators Stars: 663, Forks: 49. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Open PRs: 1, open issues: 10. Last activity: 9mo ago. Community health: 85%. Top contributors: ljharb, ahuth, HawkeyePierce89, lifeiscontent, Teaflavored, brucewpaul, znarf, gilbox, sibnerian, lencioni and others.