Skip to content

Conversation

@cabauman
Copy link
Contributor

What kind of change does this PR introduce?

  1. Mark ReactiveFragment and ReactivePreferenceFragment (core ReactiveUI project) as obsolete.

Fragment and PreferenceFragment were deprecated in API level 28:
https://developer.android.com/reference/android/preference/PreferenceFragment
https://developer.android.com/reference/android/app/Fragment

  1. Adds a ReactivePreferenceFragment to ReactiveUI.AndroidX and ReactiveUI.AndroidSupport projects as alternatives to the obsolete one.

What is the current behavior?

Users can use these classes without warning.

What is the new behavior?

Users will be warned about these classes being obsolete, and encouraged to use the AndroidX or AndroidSupport equivalents.

What might this PR break?
Nothing.

Please check if the PR fulfills these requirements

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Other information:

@cabauman cabauman requested review from a team, RLittlesII and glennawatson March 21, 2020 09:39
@glennawatson
Copy link
Contributor

After this one is merged can you please comment on #2367 with @dependabot rebase thanks.

@cabauman cabauman merged commit 77474a7 into reactiveui:master Mar 21, 2020
@lock lock bot locked and limited conversation to collaborators Jun 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants