[docs] Concept: secret quick-copy for links from search results (#23948)# Why I copy links from the docs dozens of times a day for support responses, Discord, etc., and I'm sure I'm not the only
[docs] Concept: secret quick-copy for links from search results (#23948)# Why I copy links from the docs dozens of times a day for support responses, Discord, etc., and I'm sure I'm not the only one. I typically memorize what search results give me what links. I don't need to watch the search result page load, except so that I can copy that link. So, I was wondering... what if I didn't have to? What if I could get the link without ever leaving the search results? I'm not very confident this is right way to do it, so I wanted to ask (in the form of the PR), does anybody else want this? And what would be the right way to do it? # How I've been using Linux a lot lately, which is big on copying-via-middle-click. Unfortunately, macOS doesn't have middle-click, so, it would have to be right-click, so all I did was suppress the context menu when right-clicking on a search result. If it worked like this, IMO it'd be better with some actual feedback, like a toast. Or it could be something like this copy feedback:  (just didn't want to go too far without feedback on the concept itself) Is there another sort of secret shortcut that could work? Like a keypress + click? # 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. --> # 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: Simek <[email protected]>
show more ...
refactor(cli): enable inspector proxy with network support by default (#22936)# Why Flipping this switch to be opt-out for SDK 49. # How - Renamed `EXPO_USE_CUSTOM_INSPECTOR_PROXY=true` to
refactor(cli): enable inspector proxy with network support by default (#22936)# Why Flipping this switch to be opt-out for SDK 49. # How - Renamed `EXPO_USE_CUSTOM_INSPECTOR_PROXY=true` to `EXPO_NO_INSPECTOR_PROXY=false` > This change made more sense as you would have to set `EXPO_USE_CUSTOM_INSPECTOR_PROXY=false` to revert back to the original (Metro) inspector proxy. # Test Plan - `$ EXPO_DEBUG=true expo start` -> should mention `Expo inspector proxy enabled` in the debug logs. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] 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: Expo Bot <[email protected]>
[docs] Expo CLI: improve env variables readability (#21660)
[docs] migrate to new styleguide packages (#21557)
[docs] tweaks related to the new color palette (#20818)
[docs] Add radix colors (#20397)# Why I updated the styleguide to use Radix colors. This PR adds the new version of styleguide to the docs and changes all the color, shadow, and border-radius
[docs] Add radix colors (#20397)# Why I updated the styleguide to use Radix colors. This PR adds the new version of styleguide to the docs and changes all the color, shadow, and border-radius values. # How - Very carefully finding + replacing values. - Also used `tsc` to find spots where I missed. # Test Plan I looked through the docs for awhile and fixed up a lot of spots that did not look correct. However, there may be more spots out there, so please click through the website and report any color issues that appear in this PR and not in production. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
[docs] small batch of tweaks and fixes (#20673)Co-authored-by: Tomasz Sapeta <[email protected]>
[docs] switch to the new font system introduced in Next 13 (#20536)
[docs] use mostly new components to render MDX files, unify links appearance (#20429)
[docs] implement new Callouts, support type passing in MDs (#19238)
[docs] ToC tags hotfixes (#18459)
[docs] refactor Tag components, display tags in ToC (#18351)