<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in NotificationPresenterModule.js</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>db1c4130 - [expo-notifications] Add preliminary &quot;support&quot; for Web (#8853)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPresenterModule.js#db1c4130</link>
        <description>[expo-notifications] Add preliminary &quot;support&quot; for Web (#8853)# WhyEven though we don&apos;t support Web in `expo-notifications`, we don&apos;t want to be a pain to the users and throw errors just because of running the code on Web.# HowAdded simple object fallbacks for missing modules on web so that they are queryable by```tsif (!Module.methodAsync) {  throw new Unavailability&#8230;}```Swapped `.ts` + `.web.ts` for `.native.ts` + `.ts` (or + `.web.ts` + `.ts` where it made sense, eg. if we would need to use `localStorage` inside the `.ts` file I renamed it to `.web.ts` and added an empty fallback in `.ts`).# Test Plan- [x] Ran NCL in `bare-expo` on Web, clicked buttons around, noticed the error is readable and makes sense.- [x] Ran `expo-notifications` test-suite on both iOS and Web. It seems iOS tests are a little bit flaky, unfortunately (the errors could also happen due to erroring Expo API, HTTP error 504 when fetching push token, but I was able to make all of the tests pass just refreshing).

            List of files:
            /expo/packages/expo-notifications/build/NotificationPresenterModule.js</description>
        <pubDate>Fri, 19 Jun 2020 00:29:04 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
</channel>
</rss>
