Fixes publish button #257
Open
Fixes publish button #257
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yashb196
approved these changes
May 3, 2025
rcAsironman
requested changes
May 13, 2025
There was a problem hiding this comment.
@AmarHadzic Everything works as expected, but the only issue is that the HomeScreen still freezes. Please look into it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix #253
What was changed
Previously, after a user clicked the "go-back arrow" button when editing a note, the
Publish buttonwould still appear on the homescreen instead of theaddbutton. Now, theaddbutton appears correctly.Why was it changed
The previous issue didn't allow the user to add/make new notes, hindering the user experience and making it an undesirable experience. With the fix, the user can make new notes after editing previous and new ones, enhancing the user experience.
How was it changed
state.routes[state.index].name === "HomeTab"check with a full-useNavigationState inspection of the nested stackisHomeScreenflag and based Add/Publish logic on that flagBefore clicking the add button:
After clicking the add button:
After clicking the "back" arrow button:
