You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a recent pull request #2855, a change was introduced that references Content.propTypes at runtime.
The default babel configuration for rails uses a plugin that strips the definition of propTypes out of all files for production compilation. Referencing propTypes at runtime feels like an anti-pattern which should probably be avoided, since in most cases prop-types is generally considered a dev tool and configured as a dev dependency.
Do you want to request a feature or report a bug?
bug
What's the current behavior?
In a recent pull request #2855, a change was introduced that references
Content.propTypes
at runtime.The default babel configuration for rails uses a plugin that strips the definition of propTypes out of all files for production compilation. Referencing propTypes at runtime feels like an anti-pattern which should probably be avoided, since in most cases prop-types is generally considered a dev tool and configured as a dev dependency.
The offending line is https://github.com/ianstormtaylor/slate/blob/master/packages/slate-react/src/components/content.js#L542
The text was updated successfully, but these errors were encountered: