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

DRAFT: Open post details and member views in modals at the root navigation l… #348

Open
wants to merge 5 commits into
base: dev
Choose a base branch
from

Conversation

thomasgwatson
Copy link
Collaborator

@thomasgwatson thomasgwatson commented Mar 4, 2025

…evel

A few follow up things touched on here:
#323 (comment)

TODO:

  • switch burger to back chervon

@lorenjohnson lorenjohnson marked this pull request as draft March 4, 2025 09:20
@thomasgwatson thomasgwatson marked this pull request as ready for review March 4, 2025 23:41
Copy link
Member

@lorenjohnson lorenjohnson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@thomasgwatson I’ve reviewed and tested what is here, and it is was informative to see what it'd feel like to just have Post Detail open in a 2nd level Modal always. It didn't feel as off as I thought it might. There is currently an app-crashing bug on nav from the Stream to a Member because of a missing import in PostCard, and there are a variety of cases where I can still end-up on a non-modal stack screen which aren't yet covered here. I think we should go a different direction, and not change the architecture of where these screens are located, how we navigate to them, or how they are named. I would instead introduce a "modal-like" header with an X instead of a back button to those screens while leaving them in the stack and not in the "2nd level" modal pop-out style. I think. If we are going to only use the AuthRoot level modals then I want "full screen" style modal for these areas vs the pop-out modal so the distinction between what is "in context" and not is maintained. So please hold-off on merging this or going further in the particular implementation for the moment. I think I may just take this one over, if you're up to directing to the next/another task?

@thomasgwatson
Copy link
Collaborator Author

Yep yep.

I'll work through the Welcome Page changes

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.

2 participants