flutter_local_notifications_linux 0.5.0-dev.4

Linux implementation of the flutter_local_notifications plugin

[0.5.0-dev.4]

• Breaking change callbacks have now been reworked. onDidReceiveNotificationResponse is invoked only when the app is running. This works for when a user has selected a notification or notification action. This replaces the onSelectNotification callback that existed before
• Breaking change the NotificationAppLaunchDetails has been updated to contain an instance NotificationResponse class with the payload belonging to the NotificationResponse class. This is to allow knowing more details about what caused the app to launch e.g. if a notification action was used to do so

[0.5.0-dev.3]

• Includes changes from 0.4.2

[0.5.0-dev.2]

• Added support for notification actions

[0.5.0-dev.1]

• Bumped flutter_local_notifications_platform_interface dependency

[0.4.2]

• Bumped dependencies. Thanks to PR from Guy Luz

[0.4.1+1]

• Fixed minor casing error in 0.4.1 changelog entry

[0.4.1]

• Fix initialize() returning null all the time instead of returning an appropriate boolean value to indicate if plugin has been initialised

[0.4.0]

• Bumped dbus dependency.

[0.3.0]

• Breaking change the SelectNotificationCallback typedef now maps to a function that returns void instead of a Future<dynamic>. This change was done to better communicate the plugin doesn't actually await any asynchronous computation and is similar to how button pressed callbacks work for Flutter where they are typically use VoidCallback

[0.2.0+1]

• Fixed links to GNOME developer documentation referenced in API docs

[0.2.0]

• Fixed issue when an app using the plugin is built on the web by using conditional imports
• Changed the logic where notification IDs are saved so that $XDG_RUNTIME_DIR environment variable is not set but $TMPDIR is set, then they are saved to a file within the /$TMPDIR/APP_NAME/USER_ID/SESSION_ID directory. If $TMPDIR is not set then, it would save to /tmp/APP_NAME/USER_ID/SESSION_ID
• Fixed an issue where errors would occur if the plugin was initialised multiple times

[0.1.0+1]

• Point to types within platform interface

[0.1.0]

• Initial version for Linux