#!/bin/bash
# First, let's explore the repository structure to understand where documentation is typically placed
echo "=== Repository structure overview ==="
ls -la
echo -e "\n=== Looking for documentation directories ==="
fd -t d -I "doc" --max-depth 3
fd -t d -I "docs" --max-depth 3
echo -e "\n=== Looking for README files ==="
fd "README" --max-depth 2
echo -e "\n=== Checking packages structure ==="
ls -la packages/
echo -e "\n=== Looking at runtime-dom package structure ==="
ls -la packages/runtime-dom/
echo -e "\n=== Checking for existing documentation in runtime-dom ==="
fd -t f "README" packages/runtime-dom/
fd -t f "*.md" packages/runtime-dom/

#!/bin/bash
# Let's check the existing runtime-dom README to see how it documents exports
echo "=== Current runtime-dom README content ==="
cat packages/runtime-dom/README.md
echo -e "\n=== Let's also check the main Vue README for documentation patterns ==="
head -50 README.md
echo -e "\n=== Check for any TypeScript declaration files that might contain documentation ==="
fd --glob "*.d.ts" packages/runtime-dom/
echo -e "\n=== Look at the actual index.ts file to see current exports and any existing documentation ==="
cat packages/runtime-dom/src/index.ts
echo -e "\n=== Check if there are JSDoc comments in nodeOps and patchProp files ==="
head -20 packages/runtime-dom/src/nodeOps.ts
echo "..."
head -20 packages/runtime-dom/src/patchProp.ts

#!/bin/bash
# Let's check if there's a contributing guide that mentions documentation practices
echo "=== Looking for contributing guidelines ==="
fd "CONTRIBUTING" --max-depth 2
# Check the .github directory for any documentation guidelines
echo -e "\n=== Checking .github directory ==="
ls -la .github/
# Let's see if there are any existing JSDoc comments for similar exports in the codebase
echo -e "\n=== Looking for JSDoc patterns in similar exports ==="
rg -A 5 -B 2 "export.*{.*}" packages/runtime-dom/src/index.ts
# Check if there are any official Vue.js documentation repositories or links
echo -e "\n=== Looking for any documentation-related files ==="
rg -i "documentation|docs" README.md
# Let's also check what nodeOps and patchProp actually are
echo -e "\n=== Full nodeOps file to understand what it exports ==="
tail -50 packages/runtime-dom/src/nodeOps.ts
echo -e "\n=== Full patchProp file to understand what it exports ==="
tail -50 packages/runtime-dom/src/patchProp.ts

#!/bin/bash
# Let's check the contributing guide to see if it mentions documentation practices
echo "=== Checking contributing guide for documentation practices ==="
cat .github/contributing.md
# Also check if there are any existing JSDoc comments in the codebase for reference
echo -e "\n=== Looking for JSDoc examples in runtime-dom ==="
rg -B 2 -A 2 "/\*\*" packages/runtime-dom/src/ --type ts
# Let's see the complete nodeOps and patchProp exports to understand their structure
echo -e "\n=== Complete nodeOps export structure ==="
rg -A 200 "export.*nodeOps" packages/runtime-dom/src/nodeOps.ts
echo -e "\n=== Complete patchProp export structure ==="
rg -A 50 "export.*patchProp" packages/runtime-dom/src/patchProp.ts