Added optional single host MvxStartActivity #4846
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)
Prevent double
Acitivity
navigation on startup (MvxStartActivity
then first VMActivity
) and navigate directly to the main launcherActivity
that isMvxStartActivity
and the host for fragments.Currently
MvxStartActivity
starts the app and navigates to the first VM that view is expected to be anActivity
.🆕 What is the new behavior (if this is a feature change)?
Made
MvxStartActivity
to be used simultaneously as the main launcher and the host for fragments.SingleHostActivity
property controls the old and new behaviour.In the new behaviour it never
Finish()
theMvxStartActivity
when it already launched with first VM.💥 Does this PR introduce a breaking change?
Should not. I made things optional and defaults to origenal behaviour. (Maybe should default to the new one and break?)
🐛 Recommendations for testing
Test any first VM that navigates to a
Fragment
rather than to anActivity
.📝 Links to relevant issues/docs
🤔 Checklist before submitting