Skip to content

docs: Add instructions for installing dependencies and change build directory to avoid mixing Spider & dependencies. - #122

Merged
sitaowang1998 merged 7 commits into
y-scope:mainfrom
sitaowang1998:build-doc
May 6, 2025
Merged

docs: Add instructions for installing dependencies and change build directory to avoid mixing Spider & dependencies.#122
sitaowang1998 merged 7 commits into
y-scope:mainfrom
sitaowang1998:build-doc

Conversation

@sitaowang1998

@sitaowang1998 sitaowang1998 commented May 5, 2025

Copy link
Copy Markdown
Collaborator

Description

This pr adds the dependencies building using task in quick start guide. This pr also changes the build directory from build to build/spider to avoid mixing the dependencies in build/deps with cmake-related files, fixes #118.

Checklist

  • The PR satisfies the contribution guidelines.
  • This is a breaking change and that has been indicated in the PR title, OR this isn't a
    breaking change.
  • Necessary docs have been updated, OR no docs need to be updated.

Validation performed

  • Build success with new commands.

Summary by CodeRabbit

  • Documentation
    • Updated the quick start guide with a new prerequisite for Task v3.30.0+.
    • Added instructions for installing dependencies locally or system-wide.
    • Updated build and run commands to use the build/spider directory.
    • Revised README with updated dependency installation command.

@sitaowang1998
sitaowang1998 requested a review from a team as a code owner May 5, 2025 16:32
@coderabbitai

coderabbitai Bot commented May 5, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The quick start guide was revised to introduce an optional step for installing Spider dependencies locally using the task deps:lib_install command, which installs dependencies into the build/deps directory. The documentation now also references an alternative system-wide installation method. Build and run commands were updated to use the build/spider directory instead of build. The requirements section now lists Task v3.30.0+ as a prerequisite for local dependency installation.

Changes

File(s) Change Summary
docs/src/user-docs/guides-quick-start.md Updated quick start guide: added optional local dependency installation step, changed build/run directory paths, and amended requirements.
README.md Changed dependency installation command from task deps:dep_install to task deps:lib_install in setup instructions.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Task
    participant BuildSystem
    participant Client

    User->>Task: Run deps:lib_install (optional)
    Task->>BuildSystem: Install dependencies in build/deps
    User->>BuildSystem: Build using build/spider directory
    User->>Client: Run client from build/spider/client
Loading

Assessment against linked issues

Objective Addressed Explanation
Update example build directory in User docs (#118)

Possibly related PRs

Suggested reviewers

  • davidlion

📜 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 ac01b1d and bdc8f63.

📒 Files selected for processing (2)
  • README.md (1 hunks)
  • docs/src/user-docs/guides-quick-start.md (9 hunks)
✅ Files skipped from review due to trivial changes (1)
  • README.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/src/user-docs/guides-quick-start.md
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: lint
  • GitHub Check: non-storage-unit-tests (ubuntu-22.04)
  • GitHub Check: non-storage-unit-tests (ubuntu-24.04)

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (2)
docs/src/user-docs/guides-quick-start.md (2)

7-7: Ensure consistency in section titles and links

The bullet at line 7 reads “(Optional) Install Dependencies” but the corresponding section at line 69 is titled “(Optional) Installing dependencies”. Consider normalizing the phrasing (e.g. “Install dependencies”) and adding an inline link in the bullet to jump directly to that section for better discoverability.


69-75: Clarify optional dependency installation flow

The new “(Optional) Installing dependencies” section is helpful, but its placement between “Writing a task” and “Building the task” may interrupt the reader’s flow. Consider:

  • Adding a brief note about why dependencies might not be needed if managed externally.
  • Ensuring the bullet at line 7 hyperlinks to this section (auto-generated anchors or explicit links).
  • Possibly moving this block immediately before the “Building the task” section for coherence.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8f634bc and dc012ae.

📒 Files selected for processing (1)
  • docs/src/user-docs/guides-quick-start.md (8 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: non-storage-unit-tests (ubuntu-22.04)
  • GitHub Check: non-storage-unit-tests (ubuntu-24.04)
  • GitHub Check: lint
🔇 Additional comments (3)
docs/src/user-docs/guides-quick-start.md (3)

32-32: Good addition of Task requirement

Specifying Task v3.30.0+ as a prerequisite for local dependency installation helps users avoid version mismatches. This aligns nicely with the new optional deps feature.


90-91: Update build directory commands

Updating the CMake commands to target build/spider instead of build correctly reflects the new directory structure and prevents mixing dependency files with CMake artifacts.


130-130: Confirm client build target path

The client build instruction now uses build/spider --target client, which matches the updated layout and should produce the executable in the expected location.

Comment thread docs/src/user-docs/guides-quick-start.md Outdated
sitaowang1998 and others added 2 commits May 5, 2025 12:37
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

@kirkrodrigues kirkrodrigues left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

For the PR title, how about:

docs: Add instructions for installing dependencies and change build directory to avoid mixing Spider & dependencies.

Comment thread docs/src/user-docs/guides-quick-start.md Outdated
Comment thread docs/src/user-docs/guides-quick-start.md Outdated
Comment thread docs/src/user-docs/guides-quick-start.md Outdated
Comment thread docs/src/user-docs/guides-quick-start.md Outdated
Comment thread docs/src/user-docs/guides-quick-start.md
Comment thread docs/src/user-docs/guides-quick-start.md Outdated
Comment thread docs/src/user-docs/guides-quick-start.md
@sitaowang1998 sitaowang1998 changed the title docs: Add dependencies building and change build directory . docs: Add instructions for installing dependencies and change build directory to avoid mixing Spider & dependencies. May 5, 2025
sitaowang1998 and others added 4 commits May 5, 2025 19:04
Co-authored-by: kirkrodrigues <2454684+kirkrodrigues@users.noreply.github.com>
@sitaowang1998
sitaowang1998 merged commit 12b10f7 into y-scope:main May 6, 2025
@sitaowang1998
sitaowang1998 deleted the build-doc branch May 6, 2025 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update example build directory in User docs

2 participants