feat(signals): add LAT-XYZ visual ids for copy and PR references - #3931
Closed
geclos wants to merge 9 commits into
Closed
feat(signals): add LAT-XYZ visual ids for copy and PR references#3931geclos wants to merge 9 commits into
geclos wants to merge 9 commits into
Conversation
Assign each signal a stable human-readable visual id (LAT-001 style) at creation time, persist it in Postgres, expose it on API responses, and surface it in the signals list and detail UI for easy copy/reference. Includes a text parser and resolve use-case foundation for detecting visual ids mentioned in GitHub PR bodies. Co-authored-by: Gerard <gerard@latitude.so>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-authored-by: Gerard <gerard@latitude.so>
Co-authored-by: Gerard <gerard@latitude.so>
Co-authored-by: Gerard <gerard@latitude.so>
- Add visualId to direct signal inserts in workers and API integration tests - Remove extra blank line in Fern-generated Python signal types Co-authored-by: Gerard <gerard@latitude.so>
Co-authored-by: Gerard <gerard@latitude.so>
Co-authored-by: Gerard <gerard@latitude.so>
Co-authored-by: Gerard <gerard@latitude.so>
Co-authored-by: Gerard <gerard@latitude.so>
Contributor
|
superseeded by #4154 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Signals now get a stable, human-readable visual id in
LAT-001form at creation time. The id is stored in Postgres, returned by the public API, and shown in the signals list and detail UI with one-click copy.This is the foundation for referencing signals in GitHub PR titles/bodies and linking them back later.
Changes
signals.visual_id(globally unique) plussignal_visual_id_seqfor allocation; backfill existing rows ordered bycreated_at.formatSignalVisualId,extractSignalVisualIds, andresolveSignalsMentionedInTextUseCasefor parsing PR text into project-scoped signal matches.visualIdon list + detail responses; list table and detail header show the id instead of the slug.Out of scope (follow-up)
LAT-*idsTest plan
pnpm --filter @domain/signals testpnpm --filter @domain/notifications testpnpm --filter @domain/agent-dispatch testpnpm --filter @domain/signals typecheckpnpm --filter @platform/db-postgres typecheckpnpm --filter @repo/operations typecheckpnpm --filter web typecheckpnpm openapi:emitLAT-*idsCloses LAT-731
Linear Issue: LAT-731