Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bring back support for Dialogs over non-FragmentActivity host #27790

Closed
wants to merge 1 commit into from

Conversation

mganandraj
Copy link
Contributor

Summary

This commit had earlier (intentionally) stopped supporting DialogModule over non-FragmentActivity hosts.

The change was done for a genuine reason, but unfortunately, we have a number of brownfield clients within Microsoft who are finding it hard to change their host host activities in time, due to various reasons. As we expect the transition to take a while (Another 6 months), we would like to put back the support for legacy FragmentManager in DialogModule.

This change is an essential revert of the above mentioned commit.

Changelog

Bring back the support for legacy FragmentManager in DialogModule. This is required for brownfield applications who don't have ReactActivity as the host.

[CATEGORY] [TYPE] - Message

Test Plan

  1. Tested Alert dialogs over FragmentActivity and vanilla Activity.

@facebook-github-bot facebook-github-bot added CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. p: Microsoft Partner: Microsoft Partner labels Jan 16, 2020
@pull-bot
Copy link

Messages
📖

📋 Verify Changelog Format - 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.

Generated by 🚫 dangerJS against a97c29a

@mganandraj mganandraj requested a review from dulmandakh January 16, 2020 23:00
@dulmandakh
Copy link
Contributor

I'm not sure about FB opinion about supporting non-Fragment activities, @mdvacca please review. Thanks

@dulmandakh dulmandakh requested a review from mdvacca January 17, 2020 02:12
@github-actions
Copy link

github-actions bot commented Apr 1, 2023

This PR is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Apr 1, 2023
@github-actions
Copy link

github-actions bot commented Apr 9, 2023

This PR was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this Apr 9, 2023
facebook-github-bot pushed a commit that referenced this pull request Dec 5, 2023
Summary:
Changelog: [Internal]

This makes a couple objects more exact. Nothing critical, just noticed
this old branch I had created when doing some Flow upgrades in the past.

DiffTrain build for commit facebook/react@f498aa2.

Reviewed By: hoxyq

Differential Revision: D51824015

Pulled By: kassens

fbshipit-source-id: ecadc98ffb233d6458c65c38150a29ff65a10121
Othinn pushed a commit to Othinn/react-native that referenced this pull request Jan 9, 2024
Summary:
Changelog: [Internal]

This makes a couple objects more exact. Nothing critical, just noticed
this old branch I had created when doing some Flow upgrades in the past.

DiffTrain build for commit facebook/react@f498aa2.

Reviewed By: hoxyq

Differential Revision: D51824015

Pulled By: kassens

fbshipit-source-id: ecadc98ffb233d6458c65c38150a29ff65a10121
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. p: Microsoft Partner: Microsoft Partner Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants