2.0.1

Fixes:

• Notifications were not dismissible if they were created without specifying the dismissible attribute (3f3bdda)

Changelog

• Notifications were not dismissible if they were created without specifying the dismissible attribute (3f3bdda)

2.0.0

Breaking changes

Notifications with buttons

Notifications with a least one button are not marked as not dismissible by default anymore.

Guidelines to upgrade from vx.x.x to v2.x.x

You need to set the dismissible property to false to make them not dismissible.

Notifications with images

The status of notifications with images are not set to default anymore. It will give you more possibilities.

Guidelines to upgrade from vx.x.x to v2.x.x

You need to define the status for notifications with images.

Improvements

• Support Redux 4 (#78)
• Simpler Object value mapping (#73) by @stevieoj
• Add redux-devtools support to the demo website (#70) by @5achinJani

Changelog

• The status of notifications with images are not set to default anymore (7f5aadb)
• Notifications with a least one button are not marked as not dismissible by default anymore (9448cba)
• Support Redux 4 (21b4c1e)
• Simpler Object value mapping (524fce1) by @stevieoj
• Add redux-devtools support to the demo website (16a2448) by @5achinJani

1.2.0

Improvements

• Support React 16 (#62)
• Update dependencies (#63)
• Add an action creator to update or create a notification (notify) (#64)

Changelog

• Use react-addons-module/update instead of of react/lib/update (d11ffd1)
• Update react-transition-group from v1.1.2 to v2.2.1 (df1cae1)
• Support React 16 (7acda00)

1.1.4

Fixes

• null instead of empty strings for Notification DOM events (a62dc12)

1.1.3

Fixes

• Bring back PropTypes from 'prop-types' package (#53) by @GektorGrom
• Fix link to contribution guide (#56) by @ujovlado

1.1.2

Enhancements

• enable users to override position on small screen (#33) by @bryandbor

Fixes

• add notification even if image can't not be loaded (#51)

1.1.1

Changelog

• update license: MIT

1.1.0

Enhancements

• add a filter property to NotificationsSystem component to filter notifications displayed. (#44)

Fixes

• Do not mutate state in updateNotification action creator (#37)

Changelog

• Do not mutate state in updateNotification action creator (#37)
• Fix deprecation warnings in React 15.5.x (#38) by @ingro
• add a filter property to NotificationsSystem component to filter notifications displayed. (#44)

1.0.0

Breaking changes

Notification with buttons

Before, notifications with buttons were not dismissed after dismissAfter value even if dismissAfter was defined. It's not the case anymore, now, if a notification have a dismissAfter value and buttons, then the notification will disappear after dismissAfter value.

Guidelines to upgrade from v0.x.x to v1.0.0

Make sure all notifications that require a user action, have a dismissAfter value set to 0.

Default values for notifications

Now, default value for notification are configurable on the redux part, It allow you to easily use your own react components to display notifications (less logic on view part).

Guidelines to upgrade from v0.x.x to v1.0.0

If you didn't customize the default value for notifications you have add () after notificationsReducer because it now a function wrapper. See example below

Example:

import {createStore, compose, applyMiddleware} from 'redux';
import thunk from 'redux-thunk';
import {reducer as notificationsReducer} from 'reapop';

// store
const createStoreWithMiddleware = compose(
  applyMiddleware(thunk)
)(createStore);
const store = createStoreWithMiddleware(combineReducers({
    // reducer must be mounted as `notifications` !
    notifications: notificationsReducer() // notice the `()` now
    // your reducers here
  }), {});

If you customized default value for notifications, you have to:

• Remove defaultValues props of NotificationSystem component, it is useless now.
• Define these values where you imported notifications reducer and combine your reducers. See example below

Example:

import {createStore, compose, applyMiddleware} from 'redux';
import thunk from 'redux-thunk';
import {reducer as notificationsReducer} from 'reapop';

// default value for notifications
const defaultNotification = {
        status: 'info',
        position: 'tr',
        dismissible: true,
        dismissAfter: 2000,
        allowHTML: true,
        closeButton: true
      };

// store
const createStoreWithMiddleware = compose(
  applyMiddleware(thunk)
)(createStore);
const store = createStoreWithMiddleware(combineReducers({
    // reducer must be mounted as `notifications` !
    notifications: notificationsReducer(defaultNotification) // pass config here
    // your reducers here
  }), {});

New

• removeNotifications action creator to remove all notifications. (#21)

Enhancements

• New way to define default value for notifications to easily write your own react components to display notifications (less logic on view part). (#23)
• Allow string as notification id (#24)
• Update dependencies and version supported (#26)

Changelog

• Add action creator to remove all notifications (#21)
• Notification with buttons are now dismissible (#22)
• Default settings on redux part (#23)
• Allow string as notification id (#24)
• Add react-css-transition-group as npm dependency (#25)
• Update dependencies and version supported (#26)
• Improve code quality (#27)

0.6.0

Improvements

• Allow smooth collapse animation for theme - theme must implement this feature - commit d837eff
• remove all dependencies - commit 9874767
• update dev dependencies - commit 4414b04

After - Reapop (v0.6.0) with reapop-theme-wybo (v0.4.0)

Before - Reapop (v0.5.0) with reapop-theme-wybo (v0.3.0)