Skip to content

feat(stovepipe): persist and display project types - #947

Merged
mnoah1 merged 5 commits into
mainfrom
mnoah1/stovepipe-project-type
Nov 4, 2026
Merged

mnoah1 merged 5 commits into
mainfrom
mnoah1/stovepipe-project-type

Conversation

@mnoah1

@mnoah1 mnoah1 commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Intent:

  • Identify the kind of each recorded project alongside its validation result.

Changes:

  • Carry a provider-defined project_type string through resolver results, immutable facts, MySQL storage, and project-status RPCs.
  • Group the project name and classification in ProjectInfo, shared by resolver results and project discovery providers.
  • Display project types in the web table, preserving unknown and future classifications.
  • Append project_type after the existing table columns. Update existing database schemas before deploying the application; historical facts retain an unknown type.

Test Plan

Run the targeted Go and web tests plus the MySQL storage contract suite. For an existing database, add project_type as the last column before deploying the application.
The record controller and no-op resolver tests pass with ProjectInfo; formatting, lint, module tidy, and Gazelle checks also pass.

The full web check suite, MySQL storage integration suite, and Stovepipe browser E2E test pass (35 checks total).

Revert Plan

Revert the application change; the added column can remain with its empty default.

Issue Links

None — this public change has no separate issue.

@mnoah1
mnoah1 marked this pull request as ready for review October 27, 2026 15:32
@mnoah1
mnoah1 requested review from a team, behinddwalls and sbalabanov as code owners October 27, 2026 15:32
Summary:
Intent:
- Identify the kind of each recorded project alongside its validation result.

Changes:
- Carry a provider-defined project_type string through resolver results, immutable facts, MySQL storage, and project-status RPCs.
- Display project types in the web table, preserving unknown and future classifications.
- Add an existing-database migration; apply it before deploying the updated application. Historical facts retain an unknown type.
@mnoah1
mnoah1 force-pushed the mnoah1/stovepipe-project-type branch from 0762c50 to 2a439f0 Compare November 4, 2026 16:08
@mnoah1
mnoah1 enabled auto-merge November 4, 2026 16:13
@mnoah1
mnoah1 added this pull request to the merge queue Nov 4, 2026
Merged via the queue into main with commit 7a8118b Nov 4, 2026
19 checks passed
@mnoah1
mnoah1 deleted the mnoah1/stovepipe-project-type branch November 4, 2026 16:37
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.

2 participants