Add unique constraint support to Collection UI

[Copilot]

• Add aria-label to the unique checkbox for accessibility
• Wrap REQ and UNIQ checkboxes in 24px fixed-width containers to match header alignment; update spacer to 24px
• Add aria-hidden="true" to the empty spacer div

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ur-backend-web-dashboard	Ready	Preview, Comment	Apr 4, 2026 9:04am

[Copilot]

Pull request overview

Adds UI support in the web dashboard schema builder to mark top-level primitive fields as unique, so the existing backend unique-index creation can be configured during collection creation. Also cleans up tracked build output by ignoring dist and removing committed dist artifacts.

Changes:

• Add a UNIQ column and a unique checkbox for eligible fields (depth 1 + primitive types) in CreateCollection.jsx.
• Default new fields to unique: false and clear unique when switching a field to Object/Array/Ref.
• Ignore and remove apps/web-dashboard/dist build artifacts from the repo.

Reviewed changes

Copilot reviewed 2 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
apps/web-dashboard/src/pages/CreateCollection.jsx	Adds unique field support to the schema builder UI and payload.
apps/web-dashboard/.gitignore	Ignores dist to prevent build output from being tracked.
apps/web-dashboard/dist/vite.svg	Removes committed build artifact.
apps/web-dashboard/dist/index.html	Removes committed build artifact.
apps/web-dashboard/dist/assets/index-0T9gOOFg.css	Removes committed build artifact.
apps/web-dashboard/dist/logo.png	Removes committed build artifact (binary).
apps/web-dashboard/dist/LOGO_SQ.png	Removes committed build artifact (binary).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[yash-pouranik]

@copilot apply changes based on the comments in this thread

[yash-pouranik]

@coderabbitai ready to merge?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Get PR details, reviews, and comments
gh pr view 79 --repo yash-pouranik/urBackend --json title,state,mergeable,mergeStateStatus,reviews,statusCheckRollup,reviewDecision,comments

echo "---REVIEW_COMMENTS---"
gh api repos/yash-pouranik/urBackend/pulls/79/comments --jq '[.[] | {id: .id, user: .user.login, body: .body, resolved: (if .resolved then true else false end)}]' 2>/dev/null || echo "failed"

echo "---PR_REVIEWS---"
gh api repos/yash-pouranik/urBackend/pulls/79/reviews --jq '[.[] | {id: .id, user: .user.login, state: .state, body: .body}]'

echo "---CHECKS---"
gh pr checks 79 --repo yash-pouranik/urBackend 2>/dev/null || echo "No checks found"

Length of output: 8809

---

🏁 Script executed:

#!/bin/bash
# Check recent commits to see if the Copilot-requested changes were applied
gh api repos/yash-pouranik/urBackend/pulls/79/commits --jq '[.[] | {sha: .sha, message: .commit.message, date: .commit.author.date}]'

echo "---UNRESOLVED_THREADS---"
# Check if the inline review comments have been resolved
gh api repos/yash-pouranik/urBackend/pulls/79/comments --jq '[.[] | select(.user.login != "vercel") | {id: .id, user: .user.login, body: .body[0:120], resolved: .resolved}]'

Length of output: 1887

---

@yash-pouranik: Almost there — the code looks good to merge! ✅

Here's a quick status summary:

Check	Status
Merge conflicts	✅ None
CI / Vercel deployment	✅ Passing
aria-label on unique checkbox	✅ Fixed in commit eec5ce52
REQ/UNIQ 24px fixed-width containers	✅ Fixed in commit eec5ce52
aria-hidden on spacer div	✅ Fixed in commit 9b679c76
Open Copilot review threads	⚠️ 2 threads not formally resolved

The only remaining item is that the two inline Copilot review threads (accessibility label + column alignment) are still marked as unresolved, which is causing the UNSTABLE merge state. The fixes were definitely applied in the latest commits — you just need to mark those threads as resolved on the PR, and then it'll be clean to merge.