en Copyright 2015 Java http://172.16.0.5:8080/history/expo/packages/expo-notifications/src/getNotificationChannelsAsync.android.ts#8285c032 Rename unimodules imports to expo-modules-core List of files: /expo/packages/expo-notifications/src/getNotificationChannelsAsync.android.ts Fri, 13 Aug 2021 22:46:17 +0000 Tomasz Sapeta <tsapeta@users.noreply.github.com> http://172.16.0.5:8080/history/expo/packages/expo-notifications/src/getNotificationChannelsAsync.android.ts#d09fc44c [expo-notifications] Implement notification channel management (#7123)# Why We want to let developers create and choose where to send the notification. # How Implemented a simple module managing the channels. Decisions I had to make: - I didn't add the Expo channel polyfill – do you think it is necessary? I don't know if any other notifications library would do something like this and if users would benefit from it more than from setting appropriate `sound: true, vibrate: [500, 500]` in the remote push notification payload. - all the methods resolve on platforms that don't support channels, logging a helpful message with `console.debug` - all enumerable information is an `enum` in TS, and no conversion is done from TS to native and back again, I can add that if it's needed (is it?) # Test Plan Added test cases to `test-suite` — they pass on both a device supporting channels and a device not supporting channels. List of files: /expo/packages/expo-notifications/src/getNotificationChannelsAsync.android.ts Thu, 05 Mar 2020 08:06:24 +0000 Stanisław Chmiela <sjchmiela@users.noreply.github.com>