Skip to content

Conversation

tom-un
Copy link
Collaborator

@tom-un tom-un commented Nov 30, 2019

Please select one of the following

  • I am removing an existing difference between facebook/react-native and microsoft/react-native 👍
  • I am cherry-picking a change from Facebook's react-native into microsoft/react-native 👍
  • I am making a fix / change for the macOS implementation of react-native
  • I am making a change required for Microsoft usage of react-native

The Flow checks have been broken in the Microsoft react-native fork for some time. This change adds Flow, Jest, Lint, and Prettier tests to the PR tests. It also fixes Flow breaks that have been in the repo since the last merge from .59 to .60.

While fixing and testing the Flow changes I discovered that the mac keyboard scroll events were not working. This change also restores the mac keyboard scroll events (scroll by using arrow keys, etc.). The mac keyboard scrolling depends on a native ScrollView prop onKeyDown. This can easily be confused with generic key events so I renamed onKeyDown to onScrollKeyDown.

Focus areas to test

(optional)

Microsoft Reviewers: Open in CodeFlow

@pull-bot
Copy link

pull-bot commented Nov 30, 2019

Messages
📖

📋 Missing Changelog - Can you add a Changelog? To do so, add a "## Changelog" section to your PR description. A changelog entry has the following format: [CATEGORY] [TYPE] - Message.

CATEGORY may be:
  • General
  • iOS
  • Android
  • JavaScript
  • Internal (for changes that do not need to be called out in the release notes)

TYPE may be:

  • Added, for new features.
  • Changed, for changes in existing functionality.
  • Deprecated, for soon-to-be removed features.
  • Removed, for now removed features.
  • Fixed, for any bug fixes.
  • Security, in case of vulnerabilities.

MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

📖 📋 Missing Test Plan - Can you add a Test Plan? To do so, add a "## Test Plan" section to your PR description. A Test Plan lets us know how these changes were tested.
📖 📋 Missing Summary - Can you add a Summary? To do so, add a "## Summary" section to your PR description. This is a good place to explain the motivation for making this change.

Generated by 🚫 dangerJS against 43e4fd0

@tom-un tom-un merged commit fe9ccbc into microsoft:master Dec 1, 2019
@tom-un tom-un deleted the tomun/fixflow branch May 8, 2020 21:48
christophpurrer pushed a commit to christophpurrer/react-native-macos that referenced this pull request Jul 23, 2025
Summary:
Pull Request resolved: facebook#52793

Changelog: [Internal] - Update `react-native/debugger-frontend` from 8dc0d5b...a7e4f59

Resyncs `react-native/debugger-frontend` from GitHub - see `rn-chrome-devtools-frontend` [changelog](facebook/react-native-devtools-frontend@8dc0d5b...a7e4f59).

### Changelog

[General][Fixed] fixed stack trace parsing failure for certain frames that are special to Hermes that do not exist in V8.

| Commit | Author | Date/Time | Subject |
| ------ | ------ | --------- | ------- |
| [a7e4f5967](facebook/react-native-devtools-frontend@a7e4f5967) | Vitali Zaidman (vzaidman@gmail.com) | 2025-07-23T17:04:33+01:00 | [allow parsing special hermes eval stack trace frames (microsoft#196)](facebook/react-native-devtools-frontend@a7e4f5967) |
| [12ae91ad4](facebook/react-native-devtools-frontend@12ae91ad4) | Vitali Zaidman (vzaidman@gmail.com) | 2025-07-23T16:37:55+01:00 | [allow parsing stack traces that end with "skipping x frames" (microsoft#195)](facebook/react-native-devtools-frontend@12ae91ad4) |
| [875a31a90](facebook/react-native-devtools-frontend@875a31a90) | Vitali Zaidman (vzaidman@gmail.com) | 2025-07-15T13:45:16+01:00 | [fixed general contribution guide and added meta contribution guide in pr template (microsoft#194)](facebook/react-native-devtools-frontend@875a31a90) |

Reviewed By: huntie

Differential Revision: D78817268

fbshipit-source-id: 7e266041b3df7ecbcded6e57cb51bd4647dc835d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants