stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Load mobile issue-filing metadata in one resilient request #848

Merged
timmy merged 1 commits from timmy/847-issue-filing-metadata into main 2026-08-14 20:02:52 +00:00
Conversation 0 Commits 1 Files Changed 5 +357 -63
timmy commented 2026-08-14 20:00:21 +00:00
Owner
Copy Link

What changed

  • authorize mobile issue-filing metadata once, then load labels, milestones, and templates concurrently
  • isolate section failures so blank filing and healthy metadata remain usable
  • route searchable, restored-draft, and native repository selection through one stale-response-safe loader
  • keep the aggregate UI controller in the lazy issue-capture feature chunk

Verification

  • RED: aggregate route test failed with 404 before implementation
  • RED: aggregate client test failed because loadFilingMetadata was absent
  • RED: stale repository response test accepted old metadata before request generation was added
  • focused tests passed
  • python3 -m pytest tests/ -q → 1605 passed

Closes #847

## What changed - authorize mobile issue-filing metadata once, then load labels, milestones, and templates concurrently - isolate section failures so blank filing and healthy metadata remain usable - route searchable, restored-draft, and native repository selection through one stale-response-safe loader - keep the aggregate UI controller in the lazy issue-capture feature chunk ## Verification - RED: aggregate route test failed with 404 before implementation - RED: aggregate client test failed because `loadFilingMetadata` was absent - RED: stale repository response test accepted old metadata before request generation was added - focused tests passed - `python3 -m pytest tests/ -q` → 1605 passed Closes #847
timmy added 1 commit 2026-08-14 20:00:22 +00:00
feat: load resilient issue filing metadata
All checks were successful
CI / lint (pull_request) Successful in 1m55s
Details
CI / build-release (pull_request) Successful in 5s
Details
CI / release-candidate (pull_request) Has been skipped
Details
a226addcc4
timmy merged commit 8edc83893f into main 2026-08-14 20:02:52 +00:00
timmy deleted branch timmy/847-issue-filing-metadata 2026-08-14 20:02:52 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
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: stackchain/stackchain-dashboard#848
No description provided.
Delete Branch "timmy/847-issue-filing-metadata"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?