[NOT READY YET] feat: Add show_in_map toggle#1181
Open
eStarKee06 wants to merge 2 commits intoGreenstand:masterfrom
Open
[NOT READY YET] feat: Add show_in_map toggle#1181eStarKee06 wants to merge 2 commits intoGreenstand:masterfrom
eStarKee06 wants to merge 2 commits intoGreenstand:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This addresses the issue #1038 by adding the toggle switch on the grower detail.
Screen.Recording.2026-04-12.at.12.02.35.PM.mov
NOTE: There is a flick when the toggle is interacted with because the existing useEffect is listening to the growers state changing. I think this is something that can be improved but it will need a bit of a refactor and out of scope for this change. I can help write a separate issue for it later.
Also, I want to give credit to this existing MR in the past (2023), copy pasted the UI from this.
What kind of change(s) does this PR introduce?
Please check if the PR fulfils these requirements
Issue
What is the current behavior?
What is the new behavior?
Breaking change
Does this PR introduce a breaking change?
Other useful information