| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[guides] Add a guide on writing document titles and headings (#32199) # Why <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> Fixes ENG-13207 # How <!-- How did you build this feature or fix this bug and why? --> Add a guide on how to write document titles and section headings that can be optimized for search. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] 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 `npx expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Keith Kurak <keith.kurak@gmail.com> | 1 年前 | |
[guides] Some clarification on updating changelogs in the repo | 3 年前 | |
[guides] Update Release Workflow to add `pnpm versions-schema-sync` (#47280) # Why <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> Add missing step about generating `native-modules.json` for the sdk cut off release here: https://github.com/expo/expo/blob/main/guides/releasing/Release%20Workflow.md?rgh-link-date=2026-01-21T12%3A47%3A46Z#09-generate-new-sdk-docs # Test Plan <!-- 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. --> Proofread. # Checklist <!-- Please check the appropriate items below if they apply to your diff. --> - [ ] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) | 3 天前 | |
[cellular] Rename enums for usability, move off of main queue, touch up docs The cell generation enums were invalid JS identifiers (can't start with a digit) so I renamed them to `CELLULAR_2G` and so on. Also moved the iOS module off the main queue since it doesn't touch UI. Also made some small edits to the docs and Java error code. | 6 年前 | |
[android] Split Expo Go to unversioned and versioned flavors (#12917) * Add versioning flavors Extract `flavors.gradle` and fix versioned * Update manifest based on flavors * Update fastlane build * Unflavor versioned code * Update CI to use flavors * Set default flavor * Update guides * Update expotools versioning code [skip ci] * [wip] remove flavors from shellapps * Shell app fallback to `versioned` * Fix et paths * Bump `@expo/xdl` in `expotools` [skip ci] * Missing uncommitted changes [skip ci] -expotools yarn.lock, shell app fixes * Rebase fixes * Update "Developing Expo Go" guide [skip ci] | 4 年前 | |
[expo-go] add readme (#31770) # Why I spent some time now building Expo Go and there were some unknowns along the way, which I'd like to document. This is not a complete guide (yet) so appreciate any suggestions. One part that I removed is the section about [testing in the old guide](https://github.com/expo/expo/blob/main/guides/Developing%20Expo%20Go.md). I'm not sure the guide was up to date and would prefer someone more knowledgeable of the area documents that. # How add readme, remove old guide that wasn't very visible # Test Plan # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] 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 `npx expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Kudo Chien <kudo@expo.dev> | 1 年前 | |
[docs] Promote Vale rules severity from warning to error (#46168) # Why <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> Fix ENG-21189 # How <!-- How did you build this feature or fix this bug and why? --> - Promote multiple rules severity from `warning` to `error`. - Drop mdash rule and replace all `—` with `—`. - Add `--` check. # Test Plan <!-- 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. --> Run `pnpm lint-prose` and there should be no errors. # Checklist <!-- Please check the appropriate items below if they apply to your diff. --> - [ ] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) | 1 个月前 | |
[docs] Fix misplaced code block & update clone steps (#12922) | 5 年前 | |
chore: Update markdown files for Turborepo (#47164) This comes down to three main changes: - the npm scripts are more unified and can be documented - the `build/` outputs aren't committed anymore - there's a few ways users may validate changes, e.g. with `et check-packages` --------- Co-authored-by: Tomasz Sapeta <tsapeta@expo.dev> | 9 天前 | |
[repo] Optimize assets for expo-splash-screen, expo-processing, guides (#13139) Why --- Several of the assets were unnecessarily large. The PNG files could be optimized losslessly and the GIF files could be replaced with H.264 MP4s. It is hard to underperform GIFs. How --- Optimized the PNGs with `optipng -o7`. Converted the GIFs to MP4s with Handbrake with the same resolution and RF=24. Total reduction of this PR is 38.8 MiB. Since GitHub does not allow video tags in Markdown, I used GH's support for video uploads by manually dragging each MP4 file into a GitHub Markdown file and copying the URL. To make the expo-splash-screen README retain most of its look, I used table tags. GHM requires that video upload URLs be on their own line with a blank line above, which is why Markdown tables do not work. Test Plan --------- Preview the READMEs on GitHub itself, since GH needs to render the MP4 URLs as videos. | 4 年前 | |
[guides] Fix broken table of content links in git and code reviews (#21092) # Why I don't like broken links # How I updated the broken links with the right header anchors # Test Plan Click the links # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] 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` & EAS Build (eg: updated a module plugin). | 3 年前 | |
Promote expo-file-system/next to expo-file-system (#38404) | 10 个月前 | |
Updated README and CONTRIBUTING (#5603) * Updated contributing * Added contributing guide * Updated docs from feedback * Updated contributing * Update download-dependencies.sh * Update CONTRIBUTING.md * Update CONTRIBUTING.md * Update CONTRIBUTING.md * Update CONTRIBUTING.md * Moved code standards to a new guide * Added TOCs * Fixed TOCs * Update CONTRIBUTING.md * Updated setup scripts * Updated setup scripts * Update CONTRIBUTING.md * Update CONTRIBUTING.md Co-Authored-By: James Ide <ide@users.noreply.github.com> * Update CONTRIBUTING.md Co-Authored-By: James Ide <ide@users.noreply.github.com> * Update CONTRIBUTING.md * Update CONTRIBUTING.md * Update README.md | 6 年前 | |
[guides] Fix broken Writing Expo API documentation link (#22527) | 3 年前 | |
[android] Split Expo Go to unversioned and versioned flavors (#12917) * Add versioning flavors Extract `flavors.gradle` and fix versioned * Update manifest based on flavors * Update fastlane build * Unflavor versioned code * Update CI to use flavors * Set default flavor * Update guides * Update expotools versioning code [skip ci] * [wip] remove flavors from shellapps * Shell app fallback to `versioned` * Fix et paths * Bump `@expo/xdl` in `expotools` [skip ci] * Missing uncommitted changes [skip ci] -expotools yarn.lock, shell app fixes * Rebase fixes * Update "Developing Expo Go" guide [skip ci] | 4 年前 | |
Adopt swift-format in expo-modules-jsi (#45803) | 1 个月前 | |
[guides] Expo Client -> Expo Go (#10868) Why: See #10847 for a fuller explanation. This commit replaces references to the Expo Client app with Expo Go in our markdown guides (not docs). How: Searched for "expo client" and just "client" in `guides` and looked at each search result. Replaced "Expo Client" with "Expo Go" in several places, and often reworded sentences. I noticed an understandable lack of consistency: some sentences talked about "Expo Client" while others mentioned "the clients" or "the Expo Client". "Client" was also inconsistently capitalized. Changing the sentences for Expo Go cleared up all these inconsistencies which felt reaffirming. Test Plan: Clicked through the links in various markdown files to make sure they still work (especially the links in the Release Workflow doc). | 5 年前 | |
[guides] Add a guide on writing document titles and headings (#32199) # Why <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> Fixes ENG-13207 # How <!-- How did you build this feature or fix this bug and why? --> Add a guide on how to write document titles and section headings that can be optimized for search. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] 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 `npx expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Keith Kurak <keith.kurak@gmail.com> | 1 年前 | |
[repo] Optimize assets for expo-splash-screen, expo-processing, guides (#13139) Why --- Several of the assets were unnecessarily large. The PNG files could be optimized losslessly and the GIF files could be replaced with H.264 MP4s. It is hard to underperform GIFs. How --- Optimized the PNGs with `optipng -o7`. Converted the GIFs to MP4s with Handbrake with the same resolution and RF=24. Total reduction of this PR is 38.8 MiB. Since GitHub does not allow video tags in Markdown, I used GH's support for video uploads by manually dragging each MP4 file into a GitHub Markdown file and copying the URL. To make the expo-splash-screen README retain most of its look, I used table tags. GHM requires that video upload URLs be on their own line with a blank line above, which is why Markdown tables do not work. Test Plan --------- Preview the READMEs on GitHub itself, since GH needs to render the MP4 URLs as videos. | 4 年前 |