RemixDesktop Chainlink CRE Websocket Server#7194
Conversation
✅ Deploy Preview for reliable-cocada-166884 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ioedeveloper
force-pushed
the
chainlink-cre
branch
from
13a29c1 to
0fa6536
Compare
| this.terminalApi.logHtml(html) | ||
| } | ||
|
|
||
| logGeneratedKey(data) { |
There was a problem hiding this comment.
This could maybe be a little bit more generic...
| import { shell } from "electron"; | ||
| import crypto from "crypto"; | ||
| import { isE2ELocal } from "src/main"; | ||
| import { isE2ELocal } from "../main"; |
There was a problem hiding this comment.
please double check that change.
ioedeveloper
force-pushed
the
chainlink-cre
branch
from
a0855df to
bfe1e34
Compare
hsy822
left a comment
hsy822
left a comment
There was a problem hiding this comment.
Overall, I think the CRE inline /frontend idea makes sense. However, this branch is behind the latest QuickDapp lifecycle changes. After rebasing, are you planning to keep CRE as separate inline handling spread across the MCP handler, DappManager, preview, and deploy code? Or do you plan to implement it as a first-class target mode within the QuickDapp create/update/finalize/deploy pipeline?
ioedeveloper
force-pushed
the
chainlink-cre
branch
from
df57e4d to
40363e2
Compare
|
When clicking the Delete DApp button on the DApp detail page, there are cases where all files and folders are deleted except for the frontend folder inside default_workspace. As a result, the DApp still appears on the dashboard and is also shown in the preview. In some other cases, the files are not deleted at all, but the DApp no longer appears on the dashboard. Depending on the case, the DApp may not be deleted at all. |
|
When clicking Back(to dashboard) from the DApp detail page, the screen should be captured and the captured preview should appear on the dashboard, but it does not. |
|
ioedeveloper
force-pushed
the
chainlink-cre
branch
from
2843013 to
7a157be
Compare
Resolved conflicts by: - Keeping DappOperations refactoring with inline mode features - Using remixAILogger for all logging instead of console methods - Prioritizing master's changes while preserving new features
| `- Fallback: config.title || 'My DApp'\n` | ||
|
|
||
| // Design rules are intentionally lower priority than build/runtime correctness. | ||
| const QUICKDAPP_DESIGN_RULES = |
| export class FinalizeDAppGenerationHandler extends BaseToolHandler { | ||
| name = 'finalize_dapp_generation' | ||
| description = 'Finalize a DApp after ALL files have been written using write_file. This updates the config, notifies the UI, and opens the DApp preview. MUST be called after generate_dapp + write_file sequence is complete.' | ||
| description = 'Finalize a DApp after ALL files have been written using file_write. This updates the config, notifies the UI, and opens the DApp preview. MUST be called after generate_dapp + file_write sequence is complete.' |
3 participants
No description provided.