-
Notifications
You must be signed in to change notification settings - Fork 104
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
Introduce webpack and update eslint #183
Conversation
nikgraf
commented
Sep 8, 2015
- Internal Breaking Change: removed the 'Belle ' prefix fro display name.
- Introduced webpack for docs & examples.
- Upgraded eslint config
- Moved test-suite
- Removed all the custom copy/paste/delete scripts
…ect, Separator, TextInput, Toggle): update display name
@@ -4,6 +4,9 @@ This project adheres to [Semantic Versioning](http://semver.org/). | |||
|
|||
## To Be Released | |||
|
|||
### Changed | |||
- [Button, Card, Choice, ComboBox, Option, Placeholder, Rating, Select, Separator, TextInput, Toggle] Removed the 'Belle ' prefix from displayName | |||
|
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.
Hey Nik,
Just to double check, change in display name will not effect anyone already using belle.
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.
No and yes 😄
displayName is usually only used for debugging. Internally we also used it for propType checks. Some other people might have done the same. So if we want to comply to Semantic Versioning we would need to upgrade to 2.0 because it's a breaking change.
An alternative would be to fix this bug and go back to the old names: gaearon/babel-plugin-react-transform#15
Might be the best solution. Since we didn't really change components we can merge this now and take care about it before we do another release.
Great work Nik. |
Introduce webpack and update eslint