Skip to content

feat(projects): add custom labels to Compose metadata links - #4286

Open
kmendell wants to merge 2 commits into
mainfrom
feat_projects_add_custom_labels_to_compose_metadata_links
Open

kmendell wants to merge 2 commits into
mainfrom
feat_projects_add_custom_labels_to_compose_metadata_links

Conversation

@kmendell

@kmendell kmendell commented Oct 4, 2026 •

Copy link
Copy Markdown
Member

Checklist

  • This PR is not opened from my fork’s main branch
  • All new user-facing strings are translated via Paraglide (m.*())

What This PR Implements

Fixes: #4054

Changes Made

Testing Done

AI Tool Used (if applicable)

Additional Context

Disclaimer Greptiles Reviews use AI, make sure to check over its work.

To better help train Greptile on our codebase, if the comment is useful and valid Like the comment, if its not helpful or invalid Dislike

To have Greptile Re-Review the changes, mention greptileai.

RetriggerConfidence Score: 5/5 Tier: plus

The PR appears safe to merge, with a non-blocking editor completion issue to address.

Fix All in CodexFindings

  1. P2 Scalar links get key completions ▶
Fix with agent prompt
### Issue 1
frontend/src/lib/components/code-editor/editor.svelte:430-439
When someone edits a valid string link such as `- service`, this check treats the URL as a key. The editor then offers unrelated YAML snippets, including `service`; accepting one replaces the link value with service configuration. This makes it easy to accidentally turn a valid project link into invalid metadata.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Summary

The PR adds optional labels to Compose project links, exposes labeled links while retaining the deprecated urls response field, and updates the project page and editor guidance.

  • The latest change makes link-key completions available while starting a list item.

Reviews (2) · Last reviewed commit: "feat(projects): add custom labels to Com..."

kmendell commented Oct 4, 2026

Copy link
Copy Markdown
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@kmendell
kmendell marked this pull request as ready for review October 4, 2026 00:40
@kmendell
kmendell requested a review from a team October 4, 2026 00:40
Comment thread frontend/src/lib/components/code-editor/analysis/compose-schema.ts
@kmendell
kmendell force-pushed the feat_projects_add_custom_labels_to_compose_metadata_links branch from 4e6f259 to 08a7a65 Compare October 4, 2026 03:49
Comment on lines +430 to +439
const startingProjectLink =
!yamlContext.atKey &&
yamlContext.path.length === 3 &&
yamlContext.path[0] === 'x-arcane' &&
yamlContext.path[1] === 'urls' &&
typeof yamlContext.path[2] === 'number' &&
/^\s*-\s+[\w.-]*$/.test(context.state.doc.lineAt(context.pos).text);
if (startingProjectLink) {
yamlContext.atKey = true;
yamlContext.parentPath = yamlContext.path;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Scalar links get key completions When someone edits a valid string link such as - service, this check treats the URL as a key. The editor then offers unrelated YAML snippets, including service; accepting one replaces the link value with service configuration. This makes it easy to accidentally turn a valid project link into invalid metadata.

Prompt To Fix With AI
This is a comment left during a code review.
Path: frontend/src/lib/components/code-editor/editor.svelte
Line: 430-439

Comment:
**Scalar links get key completions** When someone edits a valid string link such as `- service`, this check treats the URL as a key. The editor then offers unrelated YAML snippets, including `service`; accepting one replaces the link value with service configuration. This makes it easy to accidentally turn a valid project link into invalid metadata.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Fix in Codex Fix in Claude Code

greptile-apps[bot]
greptile-apps Bot previously approved these changes Oct 4, 2026
@kmendell

Copy link
Copy Markdown
Member Author

@copilot resolve the merge conflicts in this pull request

…tom_labels_to_compose_metadata_links

# Conflicts:
#	backend/api/api_test.go
#	backend/pkg/projects/custom_labels.go

Co-authored-by: kmendell <25576967+kmendell@users.noreply.github.com>
@greptile-apps
greptile-apps Bot dismissed their stale review October 10, 2026 20:34

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

Copilot AI commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

@copilot resolve the merge conflicts in this pull request

Resolved the merge conflicts with main in 56d1884. Labeled Compose links stay in place, and metadata parsing now uses the context-aware logging from main.

This branch has not been deployed

No deployments
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