-
Notifications
You must be signed in to change notification settings - Fork 2
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
Improve utils coverage #11
Improve utils coverage #11
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for polishing it
@@ -3,13 +3,11 @@ import * as PropTypes from 'prop-types'; | |||
export default function chainPropTypes( | |||
propType1: PropTypes.Validator<unknown>, | |||
propType2: PropTypes.Validator<unknown>, | |||
): PropTypes.Requireable<unknown> { | |||
): PropTypes.Validator<unknown> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about this one, it should create an issue on
material-ui/packages/material-ui-utils/src/elementAcceptingRef.js
Lines 46 to 47 in 714dc1a
const elementAcceptingRef = chainPropTypes(PropTypes.element, acceptingRef); | |
elementAcceptingRef.isRequired = chainPropTypes(PropTypes.element.isRequired, acceptingRef); |
but at the same time, this looks completely safe:
var foo = () => null;
foo.isRequired = () => null;
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PropTypes.Requireable<unknown>
means there already is a isRequred
which is not true. We only assign that later.
4a699c0
into
oliviertassinari:add-typescript-utils-coverage
Move picker sources into lab (#4) Update README.md [DatePicker] Refactor pickers tests to testing-library and mocha (#5) [TimePicker] Migrate tests to testing library (#8) [DateTimePicker] Migrate tests (#9) Fix all pickers linter errors (#10) Fix all circular dependencies (#11) * Fix all circular dependencies * Enable mocha eslint rules for typescript tests [test] The last step to a green CI (#15) Migrate pickers docs (#12) Downgrade to withStyles for pickers sources (#16) Add public api exports for pickers components (#17) Consolidate component namespace and theme augmentation (#18) Describe conformance for pickers sub-components (#19) Autogenerate proptypes for typescript sources (mui#20) Proper build output (mui#21) Clear migration artifacts (mui#23) Eslint rule for lower-case test name convention (mui#24) DateRangePicker (mui#25) yarn deduplicate Remove GridListTile [DateTimePicker] Fix migration unit tests Fix types Fix typescript types migration issues Fix yarn lerna build (mui#33) Fix karma tests use window.Touch for CI karma tests Remove more outdated diff noise (mui#34) Replace not valid formats with valid ISO strings Try to fix CI touch tests Skip tests if Touch events are not supported Fix merge conflicts Actually type-check Fix safari tests Remove lowercase test name rule The casing is up to the test author. We're not the grammar police in tests. Fix lint Format Remove overzealous eslint-disable* Debug failing tests Better debugging Timezones are fun was isoString th efix? Let's find out what's failing and then skip it Branch for safari Skip DateRangePicker in browsers review Matt's review Co-authored-by: Matt <[email protected]> format docs:i18n
any
->unknown
or better)@ts-ignore