Skip to content

feat(schema-meta): Add context-aware schema metadata generation #1099

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.

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
merged 3 commits into from
Apr 4, 2025

Conversation

MH4GF
Copy link
Member

@MH4GF MH4GF commented Apr 3, 2025

Related Issue

N/A

What does this PR do?

Enhances the schema metadata generation pipeline to use existing metadata as context for generating new suggestions. The AI prompt now receives the current schema metadata file content, allowing it to build upon existing metadata rather than generating from scratch. This enables more informed and incremental improvements to schema metadata.

What should reviewers focus on?

  • Type-safe validation of existing schema metadata using Valibot's safeParse function
  • Proper handling of the current schema metadata in the generateSchemaMeta function
  • Integration with GitHub file content retrieval
  • Enhanced prompt that instructs the AI to build upon existing metadata

How has this been tested?

Tested with existing PR reviews to verify that generated schema metadata builds upon existing suggestions.

What was done

🤖 Generated by PR Agent at 7bcb668

  • Enhanced schema metadata generation with context-aware prompts.
  • Integrated GitHub file content retrieval for existing metadata.
  • Validated schema metadata using Valibot's safeParse function.
  • Updated documentation to reflect context-aware metadata generation.

Detailed Changes

Relevant files
Enhancement
processGenerateSchemaMeta.ts
Fetch and validate current schema metadata for prompts     

frontend/packages/jobs/src/functions/processGenerateSchemaMeta.ts

  • Added functionality to fetch current schema metadata from GitHub.
  • Integrated safeParse for type-safe validation of schema metadata.
  • Updated processGenerateSchemaMeta to pass current metadata to the
    prompt.
  • +26/-0   
    generateSchemaMeta.ts
    Enhance schema metadata prompt with context-awareness       

    frontend/packages/jobs/src/prompts/generateSchemaMeta/generateSchemaMeta.ts

  • Modified prompt to include current schema metadata.
  • Added guidelines to build upon existing metadata incrementally.
  • Updated function to handle current metadata as input.
  • +13/-1   
    Documentation
    progress.md
    Update progress documentation for schema metadata enhancements

    memory-bank/progress.md

  • Documented enhancements to schema metadata generation pipeline.
  • Highlighted context-aware prompts and type-safe validation.
  • +3/-3     
    systemPatterns.md
    Document system pattern for context-aware schema metadata

    memory-bank/systemPatterns.md

  • Added details on context-enriched schema metadata generation.
  • Emphasized incremental improvements using existing metadata.
  • +1/-1     
    techContext.md
    Update tech context for schema metadata improvements         

    memory-bank/techContext.md

  • Updated technical context to include schema metadata enhancements.
  • Highlighted use of existing metadata in AI prompts.
  • +1/-1     

    Additional Notes

    This change improves the quality of schema metadata suggestions by providing more context to the AI model.


    Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
  • …ing metadata for context-aware suggestions
    
    - Updated `processGenerateSchemaMeta` to fetch and validate current schema metadata from GitHub.
    - Modified `generateSchemaMeta` to accept current schema metadata, allowing for incremental improvements in suggestions.
    - Improved documentation to reflect the context-aware nature of the schema metadata generation process.
    Copy link

    vercel bot commented Apr 3, 2025

    The latest updates on your projects. Learn more about Vercel for Git ↗︎

    Name Status Preview Comments Updated (UTC)
    liam-app ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 4, 2025 6:55am
    liam-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 4, 2025 6:55am
    liam-erd-sample ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 4, 2025 6:55am

    Copy link

    changeset-bot bot commented Apr 3, 2025

    ⚠️ No Changeset found

    Latest commit: 36ae86d

    Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

    This PR includes no changesets

    When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

    Click here to learn what changesets are, and how to add one.

    Click here if you're a maintainer who wants to add a changeset to this PR

    Copy link

    supabase bot commented Apr 3, 2025

    Updates to Preview Branch (add-current-override-file-toprompt) ↗︎

    Deployments Status Updated
    Database Fri, 04 Apr 2025 06:51:01 UTC
    Services Fri, 04 Apr 2025 06:51:01 UTC
    APIs Fri, 04 Apr 2025 06:51:01 UTC

    Tasks are run on every commit but only new migration files are pushed.
    Close and reopen this PR if you want to apply changes from existing seed or migration files.

    Tasks Status Updated
    Configurations Fri, 04 Apr 2025 06:51:10 UTC
    Migrations Fri, 04 Apr 2025 06:51:12 UTC
    Seeding Fri, 04 Apr 2025 06:51:12 UTC
    Edge Functions Fri, 04 Apr 2025 06:51:12 UTC

    View logs for this Workflow Run ↗︎.
    Learn more about Supabase for Git ↗︎.

    @MH4GF MH4GF marked this pull request as ready for review April 3, 2025 06:13
    @MH4GF MH4GF requested a review from a team as a code owner April 3, 2025 06:13
    @MH4GF MH4GF requested review from hoshinotsuyoshi, FunamaYukina, junkisai and NoritakaIkeda and removed request for a team April 3, 2025 06:13
    Copy link
    Contributor

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Error Handling

    The code fetches the current schema metadata file but doesn't handle the case where the file doesn't exist yet (first-time generation). The getFileContent function might throw an error if the file doesn't exist, which should be caught and handled gracefully.

    const { content: currentSchemaMetaContent } = await getFileContent(
      repositoryFullName,
      OVERRIDE_SCHEMA_FILE_PATH,
      overallReview.branchName,
      Number(repository.installationId),
    )
    Empty Object Default

    When no current schema metadata exists, an empty object '{}' is passed to the prompt. This might not be the best representation of "no metadata exists" and could confuse the AI model since it's not a valid DBOverride structure.

    currentSchemaMeta: currentSchemaMeta
      ? JSON.stringify(currentSchemaMeta, null, 2)
      : '{}',

    Copy link
    Contributor

    qodo-merge-for-open-source bot commented Apr 3, 2025

    PR Code Suggestions ✨

    Explore these optional code suggestions:

    CategorySuggestion                                                                                                                                    Impact
    Possible issue
    Handle JSON parsing errors

    Wrap the JSON.parse call in a try-catch block to handle potential JSON parsing
    errors, as the content might not be valid JSON.

    frontend/packages/jobs/src/functions/processGenerateSchemaMeta.ts [68]

    -const parsedJson = JSON.parse(currentSchemaMetaContent)
    +try {
    +  const parsedJson = JSON.parse(currentSchemaMetaContent)
    +} catch (error) {
    +  console.error('Failed to parse schema metadata JSON:', error)
    +  // Continue with null currentSchemaMeta
    +  currentSchemaMeta = null
    +}
    • Apply this suggestion
    Suggestion importance[1-10]: 8

    __

    Why: This suggestion addresses an important error handling issue. JSON.parse can throw exceptions if the content is malformed, which could crash the application. Adding a try-catch block is a critical defensive programming practice.

    Medium
    Handle file not found

    Add error handling for the case when the file doesn't exist. The current code
    assumes the getFileContent function will return an object with a content
    property even if the file doesn't exist, which might cause runtime errors.

    frontend/packages/jobs/src/functions/processGenerateSchemaMeta.ts [58-63]

    -const { content: currentSchemaMetaContent } = await getFileContent(
    -  repositoryFullName,
    -  OVERRIDE_SCHEMA_FILE_PATH,
    -  overallReview.branchName,
    -  Number(repository.installationId),
    -)
    +let currentSchemaMetaContent = null
    +try {
    +  const result = await getFileContent(
    +    repositoryFullName,
    +    OVERRIDE_SCHEMA_FILE_PATH,
    +    overallReview.branchName,
    +    Number(repository.installationId),
    +  )
    +  currentSchemaMetaContent = result.content
    +} catch (error) {
    +  console.error('Failed to fetch schema metadata file:', error)
    +  // File might not exist, which is a valid case
    +}
    • Apply this suggestion
    Suggestion importance[1-10]: 7

    __

    Why: This suggestion improves error handling for a potential edge case where the schema metadata file doesn't exist. The current implementation might cause runtime errors if getFileContent doesn't handle missing files gracefully, making this a valuable defensive programming addition.

    Medium
    • Update

    Copy link
    Member

    @hoshinotsuyoshi hoshinotsuyoshi left a comment

    Choose a reason for hiding this comment

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

    LGTM!

    @@ -33,6 +39,8 @@ Your response must strictly follow this JSON Schema:
    3. New relationships should capture implicit connections in the data model
    4. Added columns should support better data modeling without breaking existing functionality
    5. All suggestions must maintain backwards compatibility
    6. Build upon the current schema metadata when appropriate, don't duplicate existing metadata
    7. Focus on incremental improvements rather than wholesale replacement
    Copy link
    Member

    Choose a reason for hiding this comment

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

    👍 👍

    @@ -33,6 +39,8 @@ Your response must strictly follow this JSON Schema:
    3. New relationships should capture implicit connections in the data model
    4. Added columns should support better data modeling without breaking existing functionality
    5. All suggestions must maintain backwards compatibility
    6. Build upon the current schema metadata when appropriate, don't duplicate existing metadata
    Copy link
    Member

    Choose a reason for hiding this comment

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

    don't duplicate existing metadata

    I see 👀

    @hoshinotsuyoshi
    Copy link
    Member

    some conflicts exist. please check 🙏 @MH4GF

    Copy link
    Contributor

    github-actions bot commented Apr 4, 2025

    frontend/packages/prompt-test result:

    ✅️ Promptfoo test succeeded

    ✅️ Successes ❌️ Failures ⚠️ Errors
    6 0 0

    Copy link
    Contributor

    qodo-merge-for-open-source bot commented Apr 4, 2025

    CI Feedback 🧐

    (Feedback updated until commit 36ae86d)

    A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

    Action: eval

    Failed stage: Share result [❌]

    Failed test name: promptfoo test

    Failure summary:

    The action failed because the pnpm test:prompt command failed with an error. Specifically, the error
    occurred when trying to run the promptfoo share command with an unknown option --yes (line 1077).
    The command failed with exit code 1 (line 1086).

    Additionally, there were TypeScript errors in the CLI build process related to type mismatches
    between different versions of @types/estree. The error indicates that the attributes property is
    missing in the ImportDeclaration type from one version but required in another (lines 665-677,
    779-791, 893-905).

    Relevant error logs:
    1:  ##[group]Operating System
    2:  Ubuntu
    ...
    
    164:  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
    165:  env:
    166:  PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin
    167:  ##[endgroup]
    168:  Scope: all 16 workspace projects
    169:  Lockfile is up to date, resolution step is skipped
    170:  Progress: resolved 1, reused 0, downloaded 0, added 0
    171:  Packages: +2082
    172:  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    173:  Progress: resolved 2082, reused 838, downloaded 0, added 0
    174:  Progress: resolved 2082, reused 2059, downloaded 0, added 166
    175:  Progress: resolved 2082, reused 2059, downloaded 0, added 668
    176:  Progress: resolved 2082, reused 2059, downloaded 0, added 1332
    177:  Progress: resolved 2082, reused 2059, downloaded 0, added 1979
    178:  Progress: resolved 2082, reused 2059, downloaded 0, added 2082, done
    179:  WARN  Failed to create bin at /home/runner/work/liam/liam/frontend/apps/erd-sample/node_modules/.bin/liam. ENOENT: no such file or directory, open '/home/runner/work/liam/liam/frontend/packages/cli/dist-cli/bin/cli.js'
    180:  devDependencies:
    181:  + @changesets/cli 2.27.10
    182:  + @changesets/get-github-info 0.6.0
    183:  + @changesets/types 6.0.0
    184:  + @turbo/gen 2.1.2
    185:  + syncpack 13.0.3
    186:  + turbo 2.1.2
    187:  + vercel 41.4.0
    188:  frontend/apps/docs postinstall$ fumadocs-mdx
    189:  frontend/apps/docs postinstall: [MDX] types generated
    190:  frontend/apps/docs postinstall: Done
    191:  frontend/apps/app postinstall$ cp ../../packages/db-structure/node_modules/@ruby/prism/src/prism.wasm prism.wasm
    192:  frontend/apps/app postinstall: Done
    193:  WARN  Failed to create bin at /home/runner/work/liam/liam/frontend/apps/erd-sample/node_modules/.bin/liam. ENOENT: no such file or directory, open '/home/runner/work/liam/liam/frontend/apps/erd-sample/node_modules/@liam-hq/cli/dist-cli/bin/cli.js'
    194:  Done in 9.7s
    ...
    
    199:  restore-keys: Linux-promptfoo-
    200:  
    201:  enableCrossOsArchive: false
    202:  fail-on-cache-miss: false
    203:  lookup-only: false
    204:  save-always: false
    205:  env:
    206:  PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin
    207:  ##[endgroup]
    208:  Cache not found for input keys: Linux-promptfoo-v1, Linux-promptfoo-
    209:  ##[group]Run echo "OPENAI_API_KEY=${OPENAI_API_KEY}" > .env.local
    210:  �[36;1mecho "OPENAI_API_KEY=${OPENAI_API_KEY}" > .env.local�[0m
    211:  �[36;1mpnpm test:prompt�[0m
    212:  �[36;1mrm -f .env.local�[0m
    213:  �[36;1mfailures_count=$(cat frontend/packages/prompt-test/results.json | jq .results.stats.failures)�[0m
    214:  �[36;1merrors_count=$(cat frontend/packages/prompt-test/results.json | jq .results.stats.errors)�[0m
    215:  �[36;1msuccesses_count=$(cat frontend/packages/prompt-test/results.json | jq .results.stats.successes)�[0m
    216:  �[36;1mif [ $failures_count -eq 0 ]; then�[0m
    217:  �[36;1m  if [ $errors_count -eq 0 ]; then�[0m
    218:  �[36;1m    output="✅️ Promptfoo test succeeded"�[0m
    219:  �[36;1m    exit_code=0�[0m
    220:  �[36;1m  else�[0m
    221:  �[36;1m    output="❌️ Promptfoo test failed"�[0m
    222:  �[36;1m    exit_code=1�[0m
    223:  �[36;1m  fi�[0m
    224:  �[36;1melse�[0m
    225:  �[36;1m  output="❌️ Promptfoo test failed"�[0m
    226:  �[36;1m  exit_code=1�[0m
    227:  �[36;1mfi�[0m
    228:  �[36;1mecho "output=$output" >> $GITHUB_OUTPUT�[0m
    229:  �[36;1mecho "successes_count=$successes_count" >> $GITHUB_OUTPUT�[0m
    230:  �[36;1mecho "failures_count=$failures_count" >> $GITHUB_OUTPUT�[0m
    231:  �[36;1mecho "errors_count=$errors_count" >> $GITHUB_OUTPUT�[0m
    232:  �[36;1m# NOTE: if you want treat failures as workflow error, uncomment the following line.�[0m
    233:  �[36;1m# exit $exit_code�[0m
    ...
    
    280:  ##[endgroup]
    281:  ##[group]@liam-hq/erd-core:gen
    282:  cache miss, executing 7d0c34cf20d50007
    283:  > @liam-hq/erd-core@0.1.6 gen /home/runner/work/liam/liam/frontend/packages/erd-core
    284:  > pnpm run '/^gen:.*/'
    285:  > @liam-hq/erd-core@0.1.6 gen:css /home/runner/work/liam/liam/frontend/packages/erd-core
    286:  > tcm src
    287:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/styles/variables.css.d.ts
    288:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/styles/globals.css.d.ts
    289:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/features/erd/components/ERDRenderer/ERDRenderer.module.css.d.ts
    290:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/features/erd/components/ERDContent/ERDContent.module.css.d.ts
    291:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/features/erd/components/ERDRenderer/Toolbar/DesktopToolbar.module.css.d.ts
    292:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/features/erd/components/ERDRenderer/TableDetailDrawer/TableDetailDrawer.module.css.d.ts
    293:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/features/erd/components/ERDRenderer/RelationshipEdgeParticleMarker/RelationshipEdgeParticleMarker.module.css.d.ts
    294:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/features/erd/components/ERDRenderer/LeftPane/LeftPane.module.css.d.ts
    295:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/features/erd/components/ERDRenderer/ErrorDisplay/ParseErrorDisplay.module.css.d.ts
    296:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/features/erd/components/ERDRenderer/ErrorDisplay/NetworkErrorDisplay.module.css.d.ts
    297:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/features/erd/components/ERDRenderer/ErrorDisplay/ErrorDisplay.module.css.d.ts
    298:  Wrote /home/runner/work/liam/liam/frontend/packages/erd-core/src/features/erd/components/ERDRenderer/CardinalityMarkers/CardinalityMarkers.module.css.d.ts
    ...
    
    389:  . build:vite:  * [new branch]        add-schema-meta          -> origin/add-schema-meta
    390:  . build:vite:  * [new branch]        add-suggestion-to-review-issue -> origin/add-suggestion-to-review-issue
    391:  . build:vite:  * [new branch]        add_script_to_gen_schema -> origin/add_script_to_gen_schema
    392:  . build:vite:  * [new branch]        add_script_to_gen_schema_json -> origin/add_script_to_gen_schema_json
    393:  . build:vite:  * [new branch]        add_test_table           -> origin/add_test_table
    394:  . build:vite:  * [new branch]        avoid-cp-for-windows-actions -> origin/avoid-cp-for-windows-actions
    395:  . build:vite:  * [new branch]        avoid-semicolon-logic-2  -> origin/avoid-semicolon-logic-2
    396:  . build:vite:  * [new branch]        avoid-semicolon-logic-test -> origin/avoid-semicolon-logic-test
    397:  . build:vite:  * [new branch]        before-promptfoo-experiment -> origin/before-promptfoo-experiment
    398:  . build:vite:  * [new branch]        changeset-invest1        -> origin/changeset-invest1
    399:  . build:vite:  * [new branch]        changeset-invest3        -> origin/changeset-invest3
    400:  . build:vite:  * [new branch]        changeset-release/changeset-invest1 -> origin/changeset-release/changeset-invest1
    401:  . build:vite:  * [new branch]        check-github-action      -> origin/check-github-action
    402:  . build:vite:  * [new branch]        chore/install-renovate   -> origin/chore/install-renovate
    403:  . build:vite:  * [new branch]        cli-schema-json-for-local -> origin/cli-schema-json-for-local
    404:  . build:vite:  * [new branch]        console-error-1-draft    -> origin/console-error-1-draft
    405:  . build:vite:  * [new branch]        delete-docs-vercel-deploy-erd-yml -> origin/delete-docs-vercel-deploy-erd-yml
    ...
    
    407:  . build:vite:  * [new branch]        devin/1738828298-add-multiline-comment-support -> origin/devin/1738828298-add-multiline-comment-support
    408:  . build:vite:  * [new branch]        devin/1739501885-improve-navigation-test-waits -> origin/devin/1739501885-improve-navigation-test-waits
    409:  . build:vite:  * [new branch]        devin/1740113652-update-changeset-docs -> origin/devin/1740113652-update-changeset-docs
    410:  . build:vite:  * [new branch]        devin/1741661851-optimize-github-config-validation -> origin/devin/1741661851-optimize-github-config-validation
    411:  . build:vite:  * [new branch]        devin/1741663537-github-env-validation-at-boot -> origin/devin/1741663537-github-env-validation-at-boot
    412:  . build:vite:  * [new branch]        devin/1741825670-postgresql-parser-test -> origin/devin/1741825670-postgresql-parser-test
    413:  . build:vite:  * [new branch]        devin/1743062004-investigate-issue-1005 -> origin/devin/1743062004-investigate-issue-1005
    414:  . build:vite:  * [new branch]        devin/1743586604-sentry-integration -> origin/devin/1743586604-sentry-integration
    415:  . build:vite:  * [new branch]        devin/1743649752-remove-migration-web-app -> origin/devin/1743649752-remove-migration-web-app
    416:  . build:vite:  * [new branch]        devin/1743670850-add-erd-links-to-pr-comments -> origin/devin/1743670850-add-erd-links-to-pr-comments
    417:  . build:vite:  * [new branch]        devin/1743679061-fix-branch-name-slashes -> origin/devin/1743679061-fix-branch-name-slashes
    418:  . build:vite:  * [new branch]        devin/1743736741-remove-prisma-dependencies -> origin/devin/1743736741-remove-prisma-dependencies
    419:  . build:vite:  * [new branch]        emu-pr-1033-base         -> origin/emu-pr-1033-base
    420:  . build:vite:  * [new branch]        emu-pr-1033-feature      -> origin/emu-pr-1033-feature
    421:  . build:vite:  * [new branch]        enhance-the-highlighting-of-related-table-nodes-when-hovering-usememo-1 -> origin/enhance-the-highlighting-of-related-table-nodes-when-hovering-usememo-1
    422:  . build:vite:  * [new branch]        error-message-erd-network-error -> origin/error-message-erd-network-error
    423:  . build:vite:  * [new branch]        feat-related-posts       -> origin/feat-related-posts
    ...
    
    460:  . build:vite:  * [new branch]        reduce-set-node-calling-chance-3 -> origin/reduce-set-node-calling-chance-3
    461:  . build:vite:  * [new branch]        refactor-to-testcases    -> origin/refactor-to-testcases
    462:  . build:vite:  * [new branch]        refactor_edge_cardinality_by_using_custom_mark -> origin/refactor_edge_cardinality_by_using_custom_mark
    463:  . build:vite:  * [new branch]        refactor_hidden_node_handle -> origin/refactor_hidden_node_handle
    464:  . build:vite:  * [new branch]        release-debug-branch     -> origin/release-debug-branch
    465:  . build:vite:  * [new branch]        renovate/fumadocs-mdx-11.x -> origin/renovate/fumadocs-mdx-11.x
    466:  . build:vite:  * [new branch]        renovate/langchain-0.x   -> origin/renovate/langchain-0.x
    467:  . build:vite:  * [new branch]        renovate/langchain-community-0.x -> origin/renovate/langchain-community-0.x
    468:  . build:vite:  * [new branch]        renovate/langchain-core-0.x -> origin/renovate/langchain-core-0.x
    469:  . build:vite:  * [new branch]        renovate/react-monorepo  -> origin/renovate/react-monorepo
    470:  . build:vite:  * [new branch]        renovate/supabase-supabase-js-2.x -> origin/renovate/supabase-supabase-js-2.x
    471:  . build:vite:  * [new branch]        renovate/vercel-41.x     -> origin/renovate/vercel-41.x
    472:  . build:vite:  * [new branch]        renovate/vite-6.x        -> origin/renovate/vite-6.x
    473:  . build:vite:  * [new branch]        renovate/vite-tsconfig-paths-5.x -> origin/renovate/vite-tsconfig-paths-5.x
    474:  . build:vite:  * [new branch]        renovate/vitejs-plugin-react-4.x -> origin/renovate/vitejs-plugin-react-4.x
    475:  . build:vite:  * [new branch]        revert-435-error-message-erd -> origin/revert-435-error-message-erd
    476:  . build:vite:  * [new branch]        review-suggestion-patch-suggestion -> origin/review-suggestion-patch-suggestion
    ...
    
    551:  . build:vite:  * [new tag]           @liam-hq/erd-core@0.1.0  -> @liam-hq/erd-core@0.1.0
    552:  . build:vite:  * [new tag]           @liam-hq/erd-core@0.1.1  -> @liam-hq/erd-core@0.1.1
    553:  . build:vite:  * [new tag]           @liam-hq/erd-core@0.1.2  -> @liam-hq/erd-core@0.1.2
    554:  . build:vite:  * [new tag]           @liam-hq/erd-core@0.1.3  -> @liam-hq/erd-core@0.1.3
    555:  . build:vite:  * [new tag]           @liam-hq/erd-core@0.1.4  -> @liam-hq/erd-core@0.1.4
    556:  . build:vite:  * [new tag]           @liam-hq/erd-core@0.1.5  -> @liam-hq/erd-core@0.1.5
    557:  . build:vite:  * [new tag]           @liam-hq/erd-core@0.1.6  -> @liam-hq/erd-core@0.1.6
    558:  . build:vite:  * [new tag]           @liam-hq/ui@0.0.12       -> @liam-hq/ui@0.0.12
    559:  . build:vite:  * [new tag]           @liam-hq/ui@0.0.13       -> @liam-hq/ui@0.0.13
    560:  . build:vite:  * [new tag]           @liam-hq/ui@0.0.14       -> @liam-hq/ui@0.0.14
    561:  . build:vite:  * [new tag]           @liam-hq/ui@0.0.15       -> @liam-hq/ui@0.0.15
    562:  . build:vite: �[36mvite v6.2.4 �[32mbuilding for production...�[36m�[39m
    563:  . build:vite: transforming...
    564:  . build:cli: chmod: cannot access 'dist-cli/bin/cli.js': No such file or directory
    565:  . build:cli: �[1m�[33m(!) [plugin typescript] vite.config.ts (29:13): @rollup/plugin-typescript TS2769: No overload matches this call.
    566:  . build:cli:   The last overload gave the following error.
    567:  . build:cli:     Type 'PluginOption[]' is not assignable to type 'PluginOption'.
    ...
    
    665:  . build:cli:                                                                                                                                                                                                         Property 'attributes' is missing in type 'import("/home/runner/work/liam/liam/node_modules/.pnpm/@types+estree@1.0.6/node_modules/@types/estree/index").ImportDeclaration' but required in type 'import("/home/runner/work/liam/liam/node_modules/.pnpm/@types+estree@1.0.7/node_modules/@types/estree/index").ImportDeclaration'.�[39m�[22m
    666:  . build:cli: �[1m/home/runner/work/liam/liam/frontend/packages/cli/vite.config.ts:29:13�[22m
    667:  . build:cli: �[90m
    668:  . build:cli: �[7m29�[0m   plugins: [react(), tsconfigPaths(), removeImportWasi(), setEnvPlugin()],
    669:  . build:cli: �[7m  �[0m �[91m            ~~~~~~~�[0m
    670:  . build:cli:   �[96m../../../node_modules/.pnpm/@types+estree@1.0.7/node_modules/@types/estree/index.d.ts�[0m:�[93m636�[0m:�[93m5�[0m
    671:  . build:cli:     �[7m636�[0m     attributes: ImportAttribute[];
    672:  . build:cli:     �[7m   �[0m �[96m    ~~~~~~~~~~�[0m
    673:  . build:cli:     'attributes' is declared here.
    674:  . build:cli:   �[96m../../../node_modules/.pnpm/vitest@3.0.8_@edge-runtime+vm@3.2.0_@types+debug@4.1.12_@types+node@22.9.0_jiti@2.4.2_lightni_nle5cbqnt53vrkwed4oeezwtyq/node_modules/vitest/dist/config.d.ts�[0m:�[93m82�[0m:�[93m18�[0m
    675:  . build:cli:     �[7m82�[0m declare function defineConfig(config: UserConfigExport): UserConfigExport;
    676:  . build:cli:     �[7m  �[0m �[96m                 ~~~~~~~~~~~~�[0m
    677:  . build:cli:     The last overload is declared here.
    678:  . build:cli: �[39m
    679:  . build:cli: �[1m�[33m(!) [plugin typescript] vite.config.ts (29:22): @rollup/plugin-typescript TS2769: No overload matches this call.
    680:  . build:cli:   The last overload gave the following error.
    681:  . build:cli:     Type 'PluginOption[]' is not assignable to type 'PluginOption'.
    ...
    
    779:  . build:cli:                                                                                                                                                                                                         Property 'attributes' is missing in type 'import("/home/runner/work/liam/liam/node_modules/.pnpm/@types+estree@1.0.6/node_modules/@types/estree/index").ImportDeclaration' but required in type 'import("/home/runner/work/liam/liam/node_modules/.pnpm/@types+estree@1.0.7/node_modules/@types/estree/index").ImportDeclaration'.�[39m�[22m
    780:  . build:cli: �[1m/home/runner/work/liam/liam/frontend/packages/cli/vite.config.ts:29:22�[22m
    781:  . build:cli: �[90m
    782:  . build:cli: �[7m29�[0m   plugins: [react(), tsconfigPaths(), removeImportWasi(), setEnvPlugin()],
    783:  . build:cli: �[7m  �[0m �[91m                     ~~~~~~~~~~~~~~~�[0m
    784:  . build:cli:   �[96m../../../node_modules/.pnpm/@types+estree@1.0.7/node_modules/@types/estree/index.d.ts�[0m:�[93m636�[0m:�[93m5�[0m
    785:  . build:cli:     �[7m636�[0m     attributes: ImportAttribute[];
    786:  . build:cli:     �[7m   �[0m �[96m    ~~~~~~~~~~�[0m
    787:  . build:cli:     'attributes' is declared here.
    788:  . build:cli:   �[96m../../../node_modules/.pnpm/vitest@3.0.8_@edge-runtime+vm@3.2.0_@types+debug@4.1.12_@types+node@22.9.0_jiti@2.4.2_lightni_nle5cbqnt53vrkwed4oeezwtyq/node_modules/vitest/dist/config.d.ts�[0m:�[93m82�[0m:�[93m18�[0m
    789:  . build:cli:     �[7m82�[0m declare function defineConfig(config: UserConfigExport): UserConfigExport;
    790:  . build:cli:     �[7m  �[0m �[96m                 ~~~~~~~~~~~~�[0m
    791:  . build:cli:     The last overload is declared here.
    792:  . build:cli: �[39m
    793:  . build:cli: �[1m�[33m(!) [plugin typescript] vite.config.ts (29:39): @rollup/plugin-typescript TS2769: No overload matches this call.
    794:  . build:cli:   The last overload gave the following error.
    795:  . build:cli:     Type 'PluginOption[]' is not assignable to type 'PluginOption'.
    ...
    
    893:  . build:cli:                                                                                                                                                                                                         Property 'attributes' is missing in type 'import("/home/runner/work/liam/liam/node_modules/.pnpm/@types+estree@1.0.6/node_modules/@types/estree/index").ImportDeclaration' but required in type 'import("/home/runner/work/liam/liam/node_modules/.pnpm/@types+estree@1.0.7/node_modules/@types/estree/index").ImportDeclaration'.�[39m�[22m
    894:  . build:cli: �[1m/home/runner/work/liam/liam/frontend/packages/cli/vite.config.ts:29:39�[22m
    895:  . build:cli: �[90m
    896:  . build:cli: �[7m29�[0m   plugins: [react(), tsconfigPaths(), removeImportWasi(), setEnvPlugin()],
    897:  . build:cli: �[7m  �[0m �[91m                                      ~~~~~~~~~~~~~~~~~~�[0m
    898:  . build:cli:   �[96m../../../node_modules/.pnpm/@types+estree@1.0.7/node_modules/@types/estree/index.d.ts�[0m:�[93m636�[0m:�[93m5�[0m
    899:  . build:cli:     �[7m636�[0m     attributes: ImportAttribute[];
    900:  . build:cli:     �[7m   �[0m �[96m    ~~~~~~~~~~�[0m
    901:  . build:cli:     'attributes' is declared here.
    902:  . build:cli:   �[96m../../../node_modules/.pnpm/vitest@3.0.8_@edge-runtime+vm@3.2.0_@types+debug@4.1.12_@types+node@22.9.0_jiti@2.4.2_lightni_nle5cbqnt53vrkwed4oeezwtyq/node_modules/vitest/dist/config.d.ts�[0m:�[93m82�[0m:�[93m18�[0m
    903:  . build:cli:     �[7m82�[0m declare function defineConfig(config: UserConfigExport): UserConfigExport;
    904:  . build:cli:     �[7m  �[0m �[96m                 ~~~~~~~~~~~~�[0m
    905:  . build:cli:     The last overload is declared here.
    906:  . build:cli: �[39m
    907:  . build:cli: �[1m�[33m(!) [plugin typescript] vite.config.ts (29:59): @rollup/plugin-typescript TS2769: No overload matches this call.
    908:  . build:cli:   The last overload gave the following error.
    909:  . build:cli:     Type 'PluginOption[]' is not assignable to type 'PluginOption'.
    ...
    
    1062:  Progress: resolved 600, reused 515, downloaded 42, added 0
    1063:  WARN  6 deprecated subdependencies found: glob@7.2.3, har-validator@5.1.5, inflight@1.0.6, request@2.88.2, rimraf@3.0.2, uuid@3.4.0
    1064:  Packages: +649
    1065:  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    1066:  Progress: resolved 691, reused 584, downloaded 66, added 0
    1067:  Progress: resolved 691, reused 584, downloaded 66, added 649, done
    1068:  .../node_modules/better-sqlite3 install$ prebuild-install || node-gyp rebuild --release
    1069:  .../node_modules/better-sqlite3 install: Done
    1070:  WARN  Issues with peer dependencies found
    1071:  .
    1072:  └─┬ promptfoo 0.108.0
    1073:  └─┬ nunjucks 3.2.4
    1074:  └── ✕ unmet peer chokidar@^3.3.0: found 4.0.3
    1075:  (node:2817) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
    1076:  (Use `node --trace-deprecation ...` to show where the warning was created)
    1077:  error: unknown option '--yes'
    1078:  Usage: promptfoo share [options] [evalId]
    1079:  Create a shareable URL of an eval (defaults to most recent)
    1080:  Options:
    1081:  --env-file, --env-path <path>  Path to .env file
    1082:  --show-auth                    Show username/password authentication
    1083:  information in the URL if exists (default:
    1084:  false)
    1085:  -h, --help                     display help for command
    1086:  ##[error]Process completed with exit code 1.
    1087:  ##[group]Run marocchino/sticky-pull-request-comment@52423e01640425a022ef5fd42c6fb5f633a02728
    1088:  with:
    1089:  message: frontend/packages/prompt-test result:
    1090:  
    1091:  
    1092:  
    1093:  ✅️ Promptfoo test succeeded
    1094:  
    1095:  | ✅️ Successes | ❌️ Failures | ⚠️ Errors |
    1096:  | --- | --- | --- |
    

    @hoshinotsuyoshi hoshinotsuyoshi added this pull request to the merge queue Apr 4, 2025
    Merged via the queue into main with commit 36f69aa Apr 4, 2025
    20 of 21 checks passed
    @hoshinotsuyoshi hoshinotsuyoshi deleted the add-current-override-file-toprompt branch April 4, 2025 06:59
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    2 participants