nsaspy/auto-dig-quasar
1
0
Fork 0
Code Issues 9 Pull requests 9 Projects Releases Packages Wiki Activity Actions 1

Use the Auto-Dig bridge dataset to scope the graph #8

Open
lost-rob0t wants to merge 3 commits from agent/use-bridge-dataset-scope into main
pull from: agent/use-bridge-dataset-scope
merge into: nsaspy:main
Conversation 1 Commits 3 Files changed 3 +70 -2
lost-rob0t commented 2026-08-02 22:25:13 +00:00 (Migrated from github.com)
Copy link

What changed

  • Synchronize the active dataset reported by the Auto-Dig bridge into Quasar's own dataset URL parameter.
  • Emit popstate after the history replacement so React Router immediately re-renders the graph projection.
  • Preserve existing query parameters, routes, and hashes.
  • Add regression coverage for URL construction and browser history/event synchronization.

Root cause

The existing graph filter only had a reliable dataset when Quasar's own URL contained ?dataset=... or when a same-origin parent referrer supplied it. In the actual embedded deployment, the parent can be cross-origin, so the referrer is intentionally rejected. Although the Auto-Dig bridge already reported the active dataset, GraphPage never received that scope and continued rendering every dataset in the shared local corpus.

Impact

Selecting an Auto-Dig dataset now immediately constrains the embedded graph to that dataset instead of exposing documents from previously loaded datasets.

Validation

  • Added Vitest coverage for bridge-driven URL scoping.
  • Branch is based directly on current main with only the runtime and dataset-scope files changed.
## What changed - Synchronize the active dataset reported by the Auto-Dig bridge into Quasar's own `dataset` URL parameter. - Emit `popstate` after the history replacement so React Router immediately re-renders the graph projection. - Preserve existing query parameters, routes, and hashes. - Add regression coverage for URL construction and browser history/event synchronization. ## Root cause The existing graph filter only had a reliable dataset when Quasar's own URL contained `?dataset=...` or when a same-origin parent referrer supplied it. In the actual embedded deployment, the parent can be cross-origin, so the referrer is intentionally rejected. Although the Auto-Dig bridge already reported the active dataset, `GraphPage` never received that scope and continued rendering every dataset in the shared local corpus. ## Impact Selecting an Auto-Dig dataset now immediately constrains the embedded graph to that dataset instead of exposing documents from previously loaded datasets. ## Validation - Added Vitest coverage for bridge-driven URL scoping. - Branch is based directly on current `main` with only the runtime and dataset-scope files changed.
lost-rob0t commented 2026-08-02 22:27:16 +00:00 (Migrated from github.com)
Copy link

Closing this as wrong-repository work. Auto-Dig Pages deploys the pinned lost-rob0t/quasar runtime with the lost-rob0t/quasar-ui submodule; it does not build from this repository. The deployed fix is being applied in lost-rob0t/starintel-gpt-auto-dig by propagating the parent dataset into the iframe URL before Quasar boots.

Closing this as wrong-repository work. Auto-Dig Pages deploys the pinned `lost-rob0t/quasar` runtime with the `lost-rob0t/quasar-ui` submodule; it does not build from this repository. The deployed fix is being applied in `lost-rob0t/starintel-gpt-auto-dig` by propagating the parent dataset into the iframe URL before Quasar boots.
nsaspy changed title from WIP: Use the Auto-Dig bridge dataset to scope the graph to Use the Auto-Dig bridge dataset to scope the graph 2026-09-02 17:26:00 +00:00
Some checks failed
CI / baseline (pull_request) Has been cancelled
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin agent/use-bridge-dataset-scope:agent/use-bridge-dataset-scope
git switch agent/use-bridge-dataset-scope

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff agent/use-bridge-dataset-scope
git switch agent/use-bridge-dataset-scope
git rebase main
git switch main
git merge --ff-only agent/use-bridge-dataset-scope
git switch agent/use-bridge-dataset-scope
git rebase main
git switch main
git merge --no-ff agent/use-bridge-dataset-scope
git switch main
git merge --squash agent/use-bridge-dataset-scope
git switch main
git merge --ff-only agent/use-bridge-dataset-scope
git switch main
git merge agent/use-bridge-dataset-scope
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/auto-dig-quasar!8
No description provided.