use imported directory as project path

[Olyno]

Description

This pull request keeps the same path as the imported project, instead of duplicating it into dyad-apps folder.

[cubic-dev-ai]

cubic analysis

No issues found across 2 files. Review in cubic

[wwwillchen]

I think this change makes sense, but there's a bunch of E2E test failing. if you want to try and fix them that'll be very helpful, otherwise, I can look at this later.

[Olyno]

I would be happy to help! Unfortunately, Github CI shows empty logs.

[antont]

I would be happy to help! Unfortunately, Github CI shows empty logs.

The logs don't seem to be empty now, there are errors like this in the run here

- /Users/runner/work/dyad/dyad/node_modules/playwright/lib/common/process.js

   at helpers/test_helper.ts:1

> 1 | import { test as base, Page, expect } from "@playwright/test";
    | ^
  2 | import * as eph from "electron-playwright-helpers";
  3 | import { ElectronApplication, _electron as electron } from "playwright";
  4 | import fs from "fs";
    at Object.<anonymous> (/Users/runner/work/dyad/dyad/e2e-tests/helpers/test_helper.ts:1:1)
    at Object.<anonymous> (/Users/runner/work/dyad/dyad/e2e-tests/version_integrity.spec.ts:1:1)

Retry #2 ───────────────────────────────────────────────────────────────────────────────────────

Error: Cannot find module '@playwright/test'
Require stack:
- /Users/runner/work/dyad/dyad/e2e-tests/helpers/test_helper.ts
- /Users/runner/work/dyad/dyad/e2e-tests/version_integrity.spec.ts
- /Users/runner/work/dyad/dyad/node_modules/playwright/lib/transform/transform.js
- /Users/runner/work/dyad/dyad/node_modules/playwright/lib/common/esmLoaderHost.js
- /Users/runner/work/dyad/dyad/node_modules/playwright/lib/common/process.js

   at helpers/test_helper.ts:1

> 1 | import { test as base, Page, expect } from "@playwright/test";
    | ^
  2 | import * as eph from "electron-playwright-helpers";
  3 | import { ElectronApplication, _electron as electron } from "playwright";
  4 | import fs from "fs";
    at Object.<anonymous> (/Users/runner/work/dyad/dyad/e2e-tests/helpers/test_helper.ts:1:1)
    at Object.<anonymous> (/Users/runner/work/dyad/dyad/e2e-tests/version_integrity.spec.ts:1:1)

[graphite-app]

The check-app-name handler currently only validates if the app name exists in the database, but it should also verify if the provided source path already exists in any app record. Since the implementation now uses the original path instead of copying to a fixed location, a user could receive misleading feedback where the name check passes but the subsequent import operation fails due to a path conflict. Consider adding path uniqueness validation to this handler to provide more accurate feedback earlier in the process.

Spotted by Diamond



Is this helpful? React 👍 or 👎 to let us know.

[Olyno]

Would you like me to do that?

[Olyno]

Sorry for the delay! The error you see doesn't seem to come from the PR itself, except if i misunderstood something. @antont