Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add script for generate typedoc declaration json file #2507

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MrKou47
Copy link
Member

@MrKou47 MrKou47 commented Jan 14, 2025

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Summary by CodeRabbit

  • Chores
    • Updated .gitignore to exclude docs/api directory
    • Enhanced typedoc.sh script to automate TypeScript documentation generation

Copy link

coderabbitai bot commented Jan 14, 2025

Walkthrough

The pull request introduces changes to the project's documentation and build process. A new entry was added to the .gitignore file to exclude the docs/api directory from version control. Simultaneously, the scripts/typedoc.sh script was updated to automate the generation of TypeScript declaration files using Typedoc, streamlining the documentation generation process for packages in the project.

Changes

File Change Summary
.gitignore Added docs/api to ignore documentation API directory
scripts/typedoc.sh Enhanced script to automate TypeDoc documentation generation for package directories

Poem

🐰 Docs hidden from Git's prying eyes,
TypeDoc scripts now rise and compile,
API secrets tucked away tight,
Rabbit's magic makes documentation light!
Generating wisdom, line by line 🔍


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
🪧 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. (Beta)
  • @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.

@MrKou47 MrKou47 requested a review from GuoLei1990 January 14, 2025 12:00
Copy link

codecov bot commented Jan 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.53%. Comparing base (3575cb9) to head (dfe05ea).
Report is 13 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2507   +/-   ##
=======================================
  Coverage   68.53%   68.53%           
=======================================
  Files         957      957           
  Lines      100057   100041   -16     
  Branches     8552     8552           
=======================================
- Hits        68575    68568    -7     
+ Misses      31226    31217    -9     
  Partials      256      256           
Flag Coverage Δ
unittests 68.53% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🧹 Nitpick comments (1)
scripts/typedoc.sh (1)

16-20: Enhance summary output with better formatting and error handling.

The summary section needs improvements for better output handling:

Apply these changes:

 echo "============"
-for f in ${SUCCESS[@]}; do
-  echo "[typedoc] $f";
+if [ ${#SUCCESS[@]} -eq 0 ]; then
+  echo "Warning: No TypeDoc files were generated" >&2
+  exit 1
+fi
+
+for f in "${SUCCESS[@]}"; do
+  echo "[typedoc] Generated: $f"
 done
 echo "============"
+echo "Successfully generated ${#SUCCESS[@]} TypeDoc files"
🧰 Tools
🪛 Shellcheck (0.10.0)

[error] 17-17: Double quote array expansions to avoid re-splitting elements.

(SC2068)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3881156 and dfe05ea.

📒 Files selected for processing (2)
  • .gitignore (1 hunks)
  • scripts/typedoc.sh (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • .gitignore
🧰 Additional context used
🪛 Shellcheck (0.10.0)
scripts/typedoc.sh

[error] 1-1: Tips depend on target shell and yours is unknown. Add a shebang or a 'shell' directive.

(SC2148)


[error] 17-17: Double quote array expansions to avoid re-splitting elements.

(SC2068)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: build (22.x, windows-latest)
  • GitHub Check: e2e (22.x)
  • GitHub Check: codecov

Comment on lines +5 to +14
for directory in ${ENGINE_PATH}/packages/*
do
if [ -d $directory ]; then
bn=`basename $directory`;
echo "typedoc compiling $directory"
npx $TYPEDOC --version
npx $TYPEDOC --json api/$bn.json --tsconfig $directory/tsconfig.json $directory/src/index.ts;
SUCCESS+=("api/$bn.json")
fi
done
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Improve robustness of package processing.

The main loop needs several improvements for better error handling and robustness:

Apply these changes:

+# Initialize array and create output directory
+declare -a SUCCESS=()
+mkdir -p api
+
-for directory in ${ENGINE_PATH}/packages/*
+for directory in "${ENGINE_PATH}/packages/"*
 do
-  if [ -d $directory ]; then
-    bn=`basename $directory`;
+  if [ -d "$directory" ]; then
+    bn="$(basename "$directory")"
     echo "typedoc compiling $directory"
-    npx $TYPEDOC --version
-    npx $TYPEDOC --json api/$bn.json --tsconfig $directory/tsconfig.json $directory/src/index.ts;
-    SUCCESS+=("api/$bn.json")
+    if ! npx "$TYPEDOC" --json "api/${bn}.json" \
+         --tsconfig "${directory}/tsconfig.json" \
+         "${directory}/src/index.ts"; then
+      echo "Error: TypeDoc generation failed for ${bn}" >&2
+      continue
+    fi
+    SUCCESS+=("api/${bn}.json")
   fi
 done
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
for directory in ${ENGINE_PATH}/packages/*
do
if [ -d $directory ]; then
bn=`basename $directory`;
echo "typedoc compiling $directory"
npx $TYPEDOC --version
npx $TYPEDOC --json api/$bn.json --tsconfig $directory/tsconfig.json $directory/src/index.ts;
SUCCESS+=("api/$bn.json")
fi
done
# Initialize array and create output directory
declare -a SUCCESS=()
mkdir -p api
for directory in "${ENGINE_PATH}/packages/"*
do
if [ -d "$directory" ]; then
bn="$(basename "$directory")"
echo "typedoc compiling $directory"
if ! npx "$TYPEDOC" --json "api/${bn}.json" \
--tsconfig "${directory}/tsconfig.json" \
"${directory}/src/index.ts"; then
echo "Error: TypeDoc generation failed for ${bn}" >&2
continue
fi
SUCCESS+=("api/${bn}.json")
fi
done

Comment on lines +1 to +4
# generate declaration files via typedoc

ENGINE_PATH=$(pwd)

Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Add proper script setup and error handling.

The script setup needs several improvements for robustness:

Apply these changes:

+#!/bin/bash
+set -euo pipefail
+
 # generate declaration files via typedoc
 
-ENGINE_PATH=$(pwd)
+ENGINE_PATH="$(pwd)"
+
+# Validate required environment variable
+if [ -z "${TYPEDOC:-}" ]; then
+  echo "Error: TYPEDOC environment variable is not set" >&2
+  exit 1
+fi
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
# generate declaration files via typedoc
ENGINE_PATH=$(pwd)
#!/bin/bash
set -euo pipefail
# generate declaration files via typedoc
ENGINE_PATH="$(pwd)"
# Validate required environment variable
if [ -z "${TYPEDOC:-}" ]; then
echo "Error: TYPEDOC environment variable is not set" >&2
exit 1
fi
🧰 Tools
🪛 Shellcheck (0.10.0)

[error] 1-1: Tips depend on target shell and yours is unknown. Add a shebang or a 'shell' directive.

(SC2148)

Comment on lines +1 to +20
# generate declaration files via typedoc

ENGINE_PATH=$(pwd)

for directory in ${ENGINE_PATH}/packages/*
do
if [ -d $directory ]; then
bn=`basename $directory`;
echo "typedoc compiling $directory"
npx $TYPEDOC --version
npx $TYPEDOC --json api/$bn.json --tsconfig $directory/tsconfig.json $directory/src/index.ts;
SUCCESS+=("api/$bn.json")
fi
done

echo "============"
for f in ${SUCCESS[@]}; do
echo "[typedoc] $f";
done
echo "============"
Copy link

Choose a reason for hiding this comment

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

💡 Codebase verification

TypeDoc dependency and configuration are missing

The script assumes TypeDoc is available but:

  • TypeDoc is not installed as a dependency in any package
  • The $TYPEDOC variable is undefined
  • No TypeDoc configuration file exists

This will cause documentation generation to fail. Please:

  • Add TypeDoc as a devDependency
  • Define the $TYPEDOC variable or use direct npx calls
  • Add TypeDoc configuration
🔗 Analysis chain

Verify TypeDoc setup and configuration.

Please ensure that TypeDoc is properly configured in the project:

Run this script to verify the setup:

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check TypeDoc configuration and dependencies

# Check if TypeDoc is in package.json
echo "Checking TypeDoc dependencies..."
jq '.dependencies["typedoc"] // .devDependencies["typedoc"]' package.json

# Check for TypeDoc configuration file
echo -e "\nChecking for TypeDoc configuration..."
if [ -f "typedoc.json" ]; then
  cat typedoc.json
else
  echo "Warning: No typedoc.json found"
fi

# Check packages structure
echo -e "\nVerifying packages structure..."
fd -t d . packages/ -d 1

Length of output: 692


Script:

#!/bin/bash
# Check workspace and package dependencies

echo "Checking root package.json workspace setup..."
jq '.workspaces' package.json

echo -e "\nChecking for TypeDoc in package package.json files..."
fd package.json packages/ -x jq -c '{name: .name, typedoc: (.dependencies.typedoc // .devDependencies.typedoc)}' {}

echo -e "\nSearching for TYPEDOC variable definition..."
rg "TYPEDOC=" -g '!node_modules'

Length of output: 1207

🧰 Tools
🪛 Shellcheck (0.10.0)

[error] 1-1: Tips depend on target shell and yours is unknown. Add a shebang or a 'shell' directive.

(SC2148)


[error] 17-17: Double quote array expansions to avoid re-splitting elements.

(SC2068)

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.

1 participant