-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Simplify build #1035
Simplify build #1035
Conversation
hmm, to actually make that happen I'd have to also edit |
} | ||
} | ||
return errors.join('\n\n'); | ||
} |
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.
Since the original file is under a BSD license, we should make sure that we either retain the original disclaimer as done in check-prop-type (https://github.com/ratehub/check-prop-types/blob/master/index.js#L7) or make sure the disclaimer for React is included explicitly in our bundled code -- which it wouldn't right now as we externalize React dependencies.
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.
Current prop-types
license is MIT (it was changed from BSD shortly after check-prop-types was published), as is check-prop-types - that presumably means this concern is moot, yes?
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.
Moot as moot can be
One licensing comment for check-prop-types, otherwise 👍 |
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.
💃
A few changes to get our webpack config a little more manageable...
raw-loader
was only used for the werkzeug css - I just wrapped that in js to export a string explicitly.uniqid
wasn't even being used, AFAICT. We were generating them and ignoring them. Probably was intended at some point for being able to clear errors. But that's something we've removed the vestiges of, at least for the time being. This is one more.check-prop-types
hasn't been maintained recently, and anyway if given the opportunity (by bringing it into our own src) we would make some slightly different choices anyway - the one I made already was returning all prop errors, not just the first one.