Add features to zli

[miaomiaowu0428]

1. save config button now works
2. options in exclusive group can be canceled
3. option buttons will change when load current_dir/Cargo.toml
4. zino-core: orm-xxx options will be hidden if zino: orm feature is not selected

Summary by CodeRabbit

• New Features

  • Enhanced the configuration form with dynamic visibility for the ORM settings based on user selections.
  • Introduced new API routes for saving and retrieving features from the Cargo.toml file.

• Bug Fixes

  • Improved error handling during feature fetching, ensuring a smoother user experience.

• Documentation

  • Added comments to clarify the importance of cleaning temporary directories in project initialization.

• Refactor

  • Streamlined JavaScript functions for better readability and efficiency in managing option states and UI updates.

[coderabbitai]

Walkthrough

The recent updates enhance the zino-cli project by improving the configuration interface, refining server functionality, and documenting the codebase. Key features include asynchronous data fetching for configuration options, improved API routes for managing Cargo.toml, and enhanced error handling. These modifications aim to create a more interactive user experience and streamline server interactions, all while maintaining clean code practices.

Changes

Files	Change Summary
zino-cli/public/zino-config.html	Introduced a new CSS class for element visibility, modified JavaScript functions for better interaction, and updated the initialization process to fetch features.
zino-cli/src/cli/init.rs	Added comments to clarify the cleanup of temporary template directories post-initialization; no changes to existing logic.
zino-cli/src/cli/new.rs	Added comments to document the cleanup necessity after project initialization; functionality remains unchanged.
zino-cli/src/cli/serve.rs	Enhanced the Features struct to support JSON serialization, introduced new API routes for saving and retrieving Cargo.toml features, and improved data handling.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ConfigForm
    participant Server

    User->>ConfigForm: Select ORM option
    ConfigForm->>ConfigForm: Toggle visibility of ORM settings
    ConfigForm->>Server: fetchFeatures()
    Server->>ConfigForm: Return current features
    ConfigForm->>ConfigForm: Update UI based on features

Loading

🐰 In the land of code, with hops and glee,
New features bloom like a vibrant tree.
Fetching options with a swift little dash,
The server now dances, making a splash!
From Cargo.toml with care we save,
A project reborn, oh how we rave! 🌼✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between dab306e and a6951cc.

Files selected for processing (4)

• zino-cli/public/zino-config.html (8 hunks)
• zino-cli/src/cli/init.rs (1 hunks)
• zino-cli/src/cli/new.rs (1 hunks)
• zino-cli/src/cli/serve.rs (6 hunks)

Files skipped from review due to trivial changes (2)

• zino-cli/src/cli/init.rs
• zino-cli/src/cli/new.rs

Additional comments not posted (12)

zino-cli/src/cli/serve.rs (7)

9-9: Import changes are appropriate.

The addition of Serialize is necessary for JSON serialization in the new API routes.

---

37-39: Route additions enhance API capabilities.

The new routes /save_cargo_toml and /get_current_features expand the API's functionality effectively.

---

121-121: Features struct updates are beneficial.

Deriving Serialize, Deserialize, and Default enhances data handling and API response capabilities.

---

127-173: from_path method is well-implemented.

The method effectively reads and parses Cargo.toml, handling missing dependencies gracefully.

---

Line range hint 176-234: generate_cargo_toml function improvements are effective.

Error handling is robust, and the use of taplo for formatting enhances the response structure.

---

236-243: get_current_features function changes align with error handling strategy.

Returning a zino::Result improves consistency in error handling.

---

245-261: save_cargo_toml function changes improve error handling.

The function provides clear feedback on success or failure, aligning with best practices.

zino-cli/public/zino-config.html (5)

188-190: CSS class .hidden is a useful addition.

The class allows for conditional visibility of elements, enhancing UI flexibility.

---

418-437: fetchFeatures function enhances initialization.

Asynchronous fetching ensures the UI reflects the current configuration state effectively.

---

Line range hint 483-532: change_option_state function improvements streamline UI logic.

The function effectively manages exclusive options and ORM form visibility, enhancing user interaction.

---

561-579: save-config button event listener enhances user experience.

The listener handles errors gracefully and updates the UI upon successful save.

---

581-584: window.onload event handler changes improve initial setup.

Calling fetchFeatures on load ensures the UI is initialized with the current configuration.

[photino]

👍