Skip to content

fix: prevent keyword=undefined from appearing in navigation URLs#1814

Open
DukeDeSouth wants to merge 1 commit intoGreenstand:mainfrom
DukeDeSouth:fix/issue-1813-keyword-undefined-in-url
Open

fix: prevent keyword=undefined from appearing in navigation URLs#1814
DukeDeSouth wants to merge 1 commit intoGreenstand:mainfrom
DukeDeSouth:fix/issue-1813-keyword-undefined-in-url

Conversation

@DukeDeSouth
Copy link

@DukeDeSouth DukeDeSouth commented Feb 9, 2026

Fixes #1813. When you click "Meet the Organization" or "Meet the Planter" from a tree page, the URL gets keyword=undefined stuck in it because the template literal always interpolates the keyword param even when it doesn't exist in the current URL. Now keyword is only added when it actually has a value, and the separator between query params adjusts correctly. Four spots fixed across two files, same code style, nothing else touched.

…enstand#1813)

When navigating from a tree/capture page to an organization or
planter/grower page, the keyword query parameter was always appended
to the URL — even when its value was undefined. This produced URLs
like /organizations/2836?keyword=undefined.

Now the keyword parameter is only appended when it actually has a
value. The embed parameter separator (? vs &) is also adjusted to
remain correct regardless of whether keyword is present.

Fixes Greenstand#1813

Co-authored-by: Cursor <[email protected]>
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.

Wrong link

1 participant