Skip to content

feat: frontend for Trust Service #934

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
coodos merged 2 commits into from
Mar 28, 2026
Merged

feat: frontend for Trust Service #934

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f1c5981
feat: frontend for Trust Service
coodos Mar 28, 2026
9623127
chore: lockfile
coodos Mar 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion services/ontology/schemas/reference.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"$schema": "http://json-schema.org/draft-07/schema#",
"schemaId": "7e94fada-581d-49b0-b6f5-1fe0766da360",
"schemaId": "c20e9437-02a4-4917-8cee-de35dabbdb6a",
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot Mar 28, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for the old schema ID in the codebase
echo "=== Searching for old schema ID: 7e94fada-581d-49b0-b6f5-1fe0766da360 ==="
rg -i "7e94fada-581d-49b0-b6f5-1fe0766da360" -C 3

echo -e "\n=== Searching for partial UUID patterns ==="
rg -i "7e94fada" -C 2

Repository: MetaState-Prototype-Project/prototype

Length of output: 199

🏁 Script executed:

#!/bin/bash
# Look for database migrations, seed data, or test fixtures that might reference the old ID
echo "=== Checking migrations and seed data ==="
fd -e sql -e json -e yaml -e yml -x rg -l "7e94fada-581d-49b0-b6f5-1fe0766da360" {}

echo -e "\n=== Looking for migration scripts ==="
fd migration --exec cat {}

Repository: MetaState-Prototype-Project/prototype

Length of output: 51395

🏁 Script executed:

#!/bin/bash
# Search for GraphQL queries that might use schemaId
echo "=== Searching for schemaId usage in GraphQL ==="
rg -i "schemaId" --type graphql -C 3

echo -e "\n=== Searching for schemaId in JS/TS files ==="
rg -i "schemaId" --type ts --type js -C 3

echo -e "\n=== Searching for reference schema usage ==="
rg -i "reference.*schema" --type ts --type js -C 2

Repository: MetaState-Prototype-Project/prototype

Length of output: 50445

Remove or clarify the schema ID change—verify the new ID is documented and intentional.

The old schema ID (7e94fada-581d-49b0-b6f5-1fe0766da360) has no references in the codebase, so there are no direct breaking changes to existing code. However, the schemaId field is actively used throughout the system (ontology service indexing, w3ds-gateway resolution, web3 adapter mapping, and eVault operations), making this a structural change that requires:

  • Documentation of why this schema ID is being changed or introduced
  • Confirmation that the new ID (c20e9437-02a4-4917-8cee-de35dabbdb6a) aligns with external eVault integration or system architecture
  • Clarification of the relationship to the PR's "frontend for Trust Service" objective (this is a backend schema change)
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@services/ontology/schemas/reference.json` at line 3, You changed the schemaId
value in services/ontology/schemas/reference.json from
7e94fada-581d-49b0-b6f5-1fe0766da360 to c20e9437-02a4-4917-8cee-de35dabbdb6a;
either revert the change or explicitly document and propagate it: update the
repository documentation and change-log to explain why schemaId was changed,
confirm the new UUID (c20e9437-02a4-4917-8cee-de35dabbdb6a) with the
eVault/integration owners and update any mapping tables or configuration that
reference schemaId (used by the ontology service indexing, w3ds-gateway
resolution, web3 adapter mapping, and eVault operations), and add a short note
in the PR description linking this backend schemaId change to the "frontend for
Trust Service" work so reviewers have the required context.

"title": "Reference",
"type": "object",
"properties": {
Expand Down
Loading
Loading