aws / aws/graph-explorer

Spike: expand useSearchParams for shareable/bookmarkable views

Open
#1,849 0 comments 0 reactions 0 assignees View on GitHub
internal needs-triage
Dominant language
TypeScript
Stars
481
Forks
108
Avg merge
8d 9h
Merged PRs (30d)
7

Description

## Goal

Today only `DataExplorer` uses `useSearchParams` (paging). Filter/search state elsewhere lives in component/Jotai state and is lost on refresh and not shareable via URL. Investigate using `useSearchParams` to persist view state in the URL so views are bookmarkable and shareable — works in declarative mode, no router upgrade needed.

## Expected Outcome

Inventory of view state that would benefit (filters, search, selected types, etc.), a recommendation on which to URL-encode, and the UX/product implications (e.g. hash-based sharing). Task out follow-up work if worthwhile.

> [!IMPORTANT]
> Internal only — this issue is maintained by the core team and is not accepting external contributions.

Contributor guide

Open the contributing guide

Research direction

Start with DataExplorer and its existing useSearchParams usage to understand the current paging behavior. Inventory the filter, search, and selected-type state held in components or Jotai, then assess which state could be URL-encoded in declarative mode. Done means a documented inventory, recommendation, UX implications, and follow-up tasks where appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.