fix: export more api for application

[yy-wow]

English | 简体中文

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• Built its own designer, fully self-validated

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Background and solution

What is the current behavior?

1. 移除Page插件后无法启动应用，有报错；
2. 自定义渲染器渲染失败，getRenderer执行时机较早，setRenderer还未执行；
3. 自定义渲染器调用的api有变更，需要暴露更多的api。

Issue Number: N/A

What is the new behavior?

1. 移除Page插件对应用无影响；
2. 自定义渲染器正常渲染；
3. 自定义渲染器可以调用完整的api，完成各项自定义逻辑。

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Bug Fixes

  • Enhanced stability by safely handling scenarios where underlying data may be unavailable, reducing potential runtime issues.

• New Features

  • Expanded page management functionality with added support for retrieving dynamic conditions and controller details.
  • Improved integration between rendering and application initialization, streamlining interactions for a more robust experience.

[coderabbitai]

Walkthrough

This pull request implements safe access improvements and API extensions across multiple modules. In DesignCanvas.vue, optional chaining is used when calling getPageById to avoid runtime errors. In RenderMain.ts, the active page context now includes a new getConditions method and the exported API is extended with getController. In canvas-api.ts, the API types are updated and new methods (getConditions, getController) are added. Finally, in runner.ts, the argument passed to the appCreated callback is modified to encapsulate the renderer within an object.

Changes

File(s)	Change Summary
packages/canvas/DesignCanvas/.../DesignCanvas.vue	Replaced direct call to getPageById with optional chaining (?.) for safe API access.
packages/canvas/render/.../RenderMain.ts, packages/canvas/render/.../canvas-function/canvas-api.ts	Extended API capabilities by adding getConditions and getController; updated type definitions and repositioned variable declarations for clarity.
packages/canvas/render/.../runner.ts	Modified the argument to the appCreated callback from a direct App instance to an object containing the renderer as an api property.

Suggested labels

refactor-main

Suggested reviewers

• hexqi
• chilingling

Poem

I'm a clever rabbit, hopping through the code,
With safe chains in place, no runtime errors to erode.
New methods spring to life in the digital glade,
API paths untangled, improvements finely made.
My whiskers twitch with each refactor delight,
Celebrating robust changes under the moonlight.
Hop on, code friends, into a future so bright!

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

 WARN  GET http://10.0.0.28:4873/globals error (503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/eslint error (503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/@eslint%2Fjs error (503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/@vue%2Feslint-config-typescript error (503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/eslint-plugin-vue error (503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/typescript error (503). Will retry in 10 seconds. 2 retries left.
 WARN  GET http://10.0.0.28:4873/globals error (503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/eslint error (503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/@vue%2Feslint-config-typescript error (503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/@eslint%2Fjs error (503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/eslint-plugin-vue error (503). Will retry in 1 minute. 1 retries left.
 WARN  GET http://10.0.0.28:4873/typescript error (503). Will retry in 1 minute. 1 retries left.
 ERR_PNPM_FETCH_503  GET http://10.0.0.28:4873/eslint: Service Unavailable - 503

This error happened while installing a direct dependency of /tmp/eslint

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fb88fdb and f2d7024.

📒 Files selected for processing (3)

• packages/canvas/render/src/RenderMain.ts (3 hunks)
• packages/canvas/render/src/canvas-function/canvas-api.ts (2 hunks)
• packages/canvas/render/src/runner.ts (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (3)

• packages/canvas/render/src/runner.ts
• packages/canvas/render/src/RenderMain.ts
• packages/canvas/render/src/canvas-function/canvas-api.ts

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: push-check

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.