Skip to content
This repository was archived by the owner on Oct 19, 2018. It is now read-only.

Commit f314fb6

Browse files
committed
updated CHANGELOG
1 parent b3c3404 commit f314fb6

File tree

1 file changed

+24
-1
lines changed

1 file changed

+24
-1
lines changed

CHANGELOG.md

Lines changed: 24 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ This project *tries* to adhere to [Semantic Versioning](http://semver.org/), eve
66
Changes are grouped as follows:
77
- **Added** for new features.
88
- **Changed** for changes in existing functionality.
9-
- **Deprecated** for once-stable features removed in upcoming releases.
9+
- **Deprecated** for once-stable features to be removed in upcoming releases.
1010
- **Removed** for deprecated features removed in this release.
1111
- **Fixed** for any bug fixes.
1212
- **Security** to invite users to upgrade in case of vulnerabilities.
@@ -18,6 +18,29 @@ Whitespace conventions:
1818
- 1 spaces before normal text
1919
-->
2020

21+
## [0.8.8] - 2016-07-13
22+
23+
### Added
24+
25+
- More helpful error messages on render failures (#152)
26+
- `Element#on('<my_event_name>')` subscribes `my_event_name` (#153)
27+
28+
### Changed
29+
30+
- `Element#on(:event)` subscribes to `on_event` for reactrb components and `onEvent` for native components. (#153)
31+
32+
### Deprecated
33+
34+
- `Element#(:event)` subscription to `_onEvent` is deprecated. Once you have changed params named `_on...` to `on_...` you can `require 'reactrb/new-event-name-convention.rb'` to avoid spurious react warning messages. (#153)
35+
36+
37+
### Fixed
38+
39+
- when using the Element['#container'].render... method generates spurious react error (#154)
40+
41+
42+
43+
2144
## [0.8.7] - 2016-07-08
2245

2346

0 commit comments

Comments
 (0)