<?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 Swift-test.ts</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>b47ee281 - feat(expo)!: use Expo CLI when building for development in Xcode (#21397)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/config-plugins/src/ios/__tests__/Swift-test.ts#b47ee281</link>
        <description>feat(expo)!: use Expo CLI when building for development in Xcode (#21397)# Why- Related #21396 - Use `npx expo start --dev-client` instead of `npx react-native start`when building a project from Xcode. This ensures we use the correctversion of Metro regardless of where the project is started.- It&apos;s unclear if building from Android Studio is supposed to triggerthe bundler in development but I couldn&apos;t get it to do so, so this PR isiOS-only.&lt;!--Please describe the motivation for this PR, and link to relevant GitHubissues, forums posts, or feature requests.--&gt;# How- Copy over a bunch of the default scripts from `react-native/scripts`into the same locations in `expo/scripts` to make it easy to maintainthis change and simple to migrate.I decided to omit the following as it appeared to be unused (setsRCT_METRO_PORT):```source &quot;$THIS_DIR/.packager.env&quot;```I also dropped:- Support for `$RCT_PACKAGER_LOGS_DIR`.- The `Process terminated. Press &lt;enter&gt; to close the window` log thatis presented after closing the dev server.- Support for a custom React Native CLI config (this is not supported inExpo CLI).&lt;!--How did you build this feature or fix this bug and why?--&gt;# Test Plan- TBD- Building for development from Xcode causes a terminal window running`npx expo start` will open instead of the community version.&lt;!--Please describe how you tested this change and how a reviewer couldreproduce your test, especially if this PR does not include automatedtests! If possible, please also provide terminal output and/orscreenshots demonstrating your test/reproduction.--&gt;# Checklist&lt;!--Please check the appropriate items below if they apply to your diff.This is required for changes to Expo modules.--&gt;- [ ] Documentation is up to date to reflect these changes (eg:https://docs.expo.dev and README.md).- [ ] Conforms with the [Documentation Writing StyleGuide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)- [ ] This diff will work correctly for `expo prebuild` &amp; EAS Build (eg:updated a module plugin).---------Co-authored-by: Expo Bot &lt;34669131+expo-bot@users.noreply.github.com&gt;Co-authored-by: Kudo Chien &lt;kudo@expo.dev&gt;

            List of files:
            /expo/packages/@expo/config-plugins/src/ios/__tests__/Swift-test.ts</description>
        <pubDate>Mon, 13 Mar 2023 15:59:08 +0000</pubDate>
        <dc:creator>Evan Bacon &lt;bacon@expo.io&gt;</dc:creator>
    </item>
<item>
        <title>ed3bd27b - chore(prebuild-config, config-plugins): rewrite tests to use latest template for fixtures (#21339)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/config-plugins/src/ios/__tests__/Swift-test.ts#ed3bd27b</link>
        <description>chore(prebuild-config, config-plugins): rewrite tests to use latest template for fixtures (#21339)# Why- The previous tests were using static representations of the versionedfixtures. This meant that many tests were possibly outdated.- Now that the CLI is versioned, we can test against the latesttemplates to ensure our config plugins are always up to date.&lt;!--Please describe the motivation for this PR, and link to relevant GitHubissues, forums posts, or feature requests.--&gt;# How- Pull in fixtures from the local template.- Rewrite tests to work with new fixtures.&lt;!--How did you build this feature or fix this bug and why?--&gt;# Test Plan- Tests should continue to pass.---------Co-authored-by: Expo Bot &lt;34669131+expo-bot@users.noreply.github.com&gt;

            List of files:
            /expo/packages/@expo/config-plugins/src/ios/__tests__/Swift-test.ts</description>
        <pubDate>Wed, 01 Mar 2023 18:18:27 +0000</pubDate>
        <dc:creator>Evan Bacon &lt;bacon@expo.io&gt;</dc:creator>
    </item>
<item>
        <title>082815dc - chore: migrate config, config-plugins, config-types, prebuild-config (#17958)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/@expo/config-plugins/src/ios/__tests__/Swift-test.ts#082815dc</link>
        <description>chore: migrate config, config-plugins, config-types, prebuild-config (#17958)

            List of files:
            /expo/packages/@expo/config-plugins/src/ios/__tests__/Swift-test.ts</description>
        <pubDate>Tue, 28 Jun 2022 00:09:27 +0000</pubDate>
        <dc:creator>Evan Bacon &lt;bacon@expo.io&gt;</dc:creator>
    </item>
</channel>
</rss>
