Skip to content

chore: move lint & prettier configs to root #590

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

Merged
merged 8 commits into from
Apr 29, 2025

Conversation

thucpn
Copy link
Collaborator

@thucpn thucpn commented Apr 29, 2025

Updated configs:

  • Lint: use eslint v9 for all ts packages. Plugins: eslint-js recommend, typescript recommend, prettier
  • Prettier: use "prettier-plugin-organize-imports", "prettier-plugin-tailwindcss"

Key changes:

  • move eslint packages, prettier packages, typescript packages and scripts to root
  • create-llama package hasn't apply typescript recommend rules and prettier-plugin-tailwindcss before. So that, this PR will apply these configs, also fix format and eslint errors in all files.

Summary by CodeRabbit

  • Chores
    • Centralized and updated Prettier and ESLint configurations for improved consistency across the project.
    • Added a root-level Prettier configuration and ignore file, while removing package-specific Prettier and ESLint configs.
    • Updated and streamlined development dependencies and scripts related to formatting and linting.
    • Adjusted ESLint rules and ignore patterns for better project-wide code quality management.

@thucpn thucpn requested a review from marcusschiesser April 29, 2025 07:48
Copy link

changeset-bot bot commented Apr 29, 2025

🦋 Changeset detected

Latest commit: c7b7990

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
create-llama Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

coderabbitai bot commented Apr 29, 2025

Warning

Rate limit exceeded

@thucpn has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 1 minutes and 15 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 6668fa2 and c7b7990.

📒 Files selected for processing (43)
  • .changeset/ninety-goats-draw.md (1 hunks)
  • packages/create-llama/templates/components/ui/html/chat/chat-avatar.tsx (2 hunks)
  • packages/create-llama/templates/components/ui/html/chat/chat-input.tsx (1 hunks)
  • packages/create-llama/templates/components/ui/html/chat/chat-item.tsx (1 hunks)
  • packages/create-llama/templates/components/ui/html/chat/chat-messages.tsx (1 hunks)
  • packages/create-llama/templates/components/ui/workflows/artifacts/ui_event.jsx (1 hunks)
  • packages/create-llama/templates/components/ui/workflows/deep_research/ui_event.jsx (7 hunks)
  • packages/server/next/app/components/ui/accordion.tsx (1 hunks)
  • packages/server/next/app/components/ui/alert-dialog.tsx (1 hunks)
  • packages/server/next/app/components/ui/breadcrumb.tsx (1 hunks)
  • packages/server/next/app/components/ui/card.tsx (1 hunks)
  • packages/server/next/app/components/ui/carousel.tsx (2 hunks)
  • packages/server/next/app/components/ui/chart.tsx (2 hunks)
  • packages/server/next/app/components/ui/chat/chat-avatar.tsx (1 hunks)
  • packages/server/next/app/components/ui/chat/chat-input.tsx (1 hunks)
  • packages/server/next/app/components/ui/chat/chat-section.tsx (1 hunks)
  • packages/server/next/app/components/ui/checkbox.tsx (1 hunks)
  • packages/server/next/app/components/ui/command.tsx (4 hunks)
  • packages/server/next/app/components/ui/context-menu.tsx (6 hunks)
  • packages/server/next/app/components/ui/dialog.tsx (2 hunks)
  • packages/server/next/app/components/ui/dropdown-menu.tsx (6 hunks)
  • packages/server/next/app/components/ui/hover-card.tsx (1 hunks)
  • packages/server/next/app/components/ui/input-otp.tsx (1 hunks)
  • packages/server/next/app/components/ui/input.tsx (1 hunks)
  • packages/server/next/app/components/ui/label.tsx (1 hunks)
  • packages/server/next/app/components/ui/menubar.tsx (8 hunks)
  • packages/server/next/app/components/ui/navigation-menu.tsx (3 hunks)
  • packages/server/next/app/components/ui/popover.tsx (1 hunks)
  • packages/server/next/app/components/ui/radio-group.tsx (2 hunks)
  • packages/server/next/app/components/ui/resizable.tsx (1 hunks)
  • packages/server/next/app/components/ui/scroll-area.tsx (2 hunks)
  • packages/server/next/app/components/ui/select.tsx (3 hunks)
  • packages/server/next/app/components/ui/separator.tsx (1 hunks)
  • packages/server/next/app/components/ui/sheet.tsx (1 hunks)
  • packages/server/next/app/components/ui/sidebar.tsx (11 hunks)
  • packages/server/next/app/components/ui/slider.tsx (2 hunks)
  • packages/server/next/app/components/ui/switch.tsx (1 hunks)
  • packages/server/next/app/components/ui/table.tsx (2 hunks)
  • packages/server/next/app/components/ui/tabs.tsx (2 hunks)
  • packages/server/next/app/components/ui/textarea.tsx (1 hunks)
  • packages/server/next/app/components/ui/toggle-group.tsx (1 hunks)
  • packages/server/next/app/components/ui/tooltip.tsx (1 hunks)
  • python/llama-index-server/examples/artifact/components/ui_event.jsx (1 hunks)

Walkthrough

This change centralizes and streamlines code formatting and linting configurations across the project. It introduces a new root-level Prettier configuration and ignore file, removes package-specific Prettier and ESLint configuration files, and consolidates related scripts and dependencies into the root package.json. The ESLint configuration is updated to use overrides for different packages, and ignore patterns are refined. Package-level formatting and linting scripts, as well as their dependencies, are removed from sub-packages, with all formatting and linting now managed from the project root. Additionally, numerous ESLint directive comments disabling rules are removed from source files, and minor code clarity improvements are made, such as adding explicit block scopes and fixing conditional logic.

Changes

File(s) Change Summary
.prettierignore, prettier.config.mjs Added root-level Prettier ignore and configuration files specifying paths to exclude and plugins to use.
eslint.config.mjs Updated ESLint config: added new override for packages/create-llama/** with specific rules and disabled rules, refined ignore patterns.
package.json Expanded devDependencies for formatting/linting, updated scripts to run root-level Prettier/ESLint commands, reordered scripts for clarity.
packages/create-llama/.eslintrc, .prettierignore, prettier.config.js Removed package-specific Prettier and ESLint configuration files from create-llama.
packages/create-llama/package.json Removed formatting/linting scripts and related devDependencies from create-llama.
packages/server/.prettierignore, prettier.config.mjs Deleted Prettier ignore and config files from server package.
packages/server/package.json Removed formatting/linting scripts and related devDependencies from server.
Multiple source files in packages/create-llama/ and subdirectories (e.g., helpers, templates) Removed numerous ESLint directive comments disabling rules (mostly import/no-extraneous-dependencies and turbo/no-undeclared-env-vars).
packages/create-llama/e2e/utils.ts Fixed incorrect conditional logic for string includes by splitting into two explicit checks; changed let to const for dataSourceArgs.
Various TypeScript files with switch statements (e.g., interpreter.ts, chat-tools.tsx) Added explicit block scoping braces {} around case clauses to improve clarity without changing logic.
packages/create-llama/templates/types/streaming/nextjs/app/components/ui/chat/tools/artifact.tsx Replaced concise conditional call with explicit if statement in useEffect; removed ESLint disable comments related to exhaustive deps and image linting.
Removed ESLint directive comments from test files in packages/create-llama/e2e/shared/. Removed ESLint disables for undeclared environment variables in multiple test files.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant RootPrettier
    participant RootESLint

    Developer->>RootPrettier: Run format/format:write script
    RootPrettier->>Developer: Format code using root config and ignore

    Developer->>RootESLint: Run lint script
    RootESLint->>Developer: Lint code with package-specific overrides
Loading

Possibly related PRs

  • chore: create-llama monorepo #581: Establishes the monorepo structure and initial formatting/linting setup, which is directly related to the centralization and cleanup performed in this PR.

Suggested reviewers

  • marcusschiesser

Poem

Hopping through configs, a rabbit's delight,
Centralized Prettier, all tidy and right.
No more stray ignores or scripts to maintain,
Linting and formatting, simple and plain.
With one root to rule them, the codebase feels bright—
A garden of order, from morning to night!
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

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.

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.

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.

@thucpn thucpn marked this pull request as ready for review April 29, 2025 08:47
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: 1

🧹 Nitpick comments (1)
package.json (1)

18-24: Enhance lint/format scripts with explicit file extensions
Right now eslint . and prettier . will pick up default file types, but it’s safer (and faster) to scope them to the extensions you actually use. For example:

"scripts": {
-  "lint": "eslint .",
+  "lint": "eslint --ext .js,.jsx,.ts,.tsx .",
-  "format": "prettier --ignore-unknown --cache --check .",
+  "format": "prettier --ignore-unknown --cache --check \"**/*.{js,jsx,ts,tsx,css,md}\" .",
-  "format:write": "prettier --ignore-unknown --write ."
+  "format:write": "prettier --ignore-unknown --write \"**/*.{js,jsx,ts,tsx,css,md}\" ."
}

This will ensure only relevant files are processed and can improve performance.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 241d82a and eec050e.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (11)
  • .prettierignore (1 hunks)
  • eslint.config.mjs (2 hunks)
  • package.json (1 hunks)
  • packages/create-llama/.eslintrc (0 hunks)
  • packages/create-llama/.prettierignore (0 hunks)
  • packages/create-llama/package.json (0 hunks)
  • packages/create-llama/prettier.config.js (0 hunks)
  • packages/server/.prettierignore (0 hunks)
  • packages/server/package.json (1 hunks)
  • packages/server/prettier.config.mjs (0 hunks)
  • prettier.config.mjs (1 hunks)
💤 Files with no reviewable changes (6)
  • packages/server/.prettierignore
  • packages/create-llama/.eslintrc
  • packages/create-llama/prettier.config.js
  • packages/server/prettier.config.mjs
  • packages/create-llama/package.json
  • packages/create-llama/.prettierignore
⏰ Context from checks skipped due to timeout of 90000ms (27)
  • GitHub Check: typescript (22, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: typescript (22, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: typescript (22, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: typescript (22, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (22, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: typescript (22, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: typescript (22, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (22, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: typescript (22, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --llamacloud)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --example-file)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --no-files)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --llamacloud)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --example-file)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --no-files)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --llamacloud)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --example-file)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --no-files)
🔇 Additional comments (10)
.prettierignore (1)

1-9: Effective configuration for ignoring build artifacts and dependencies

This new root-level .prettierignore file appropriately excludes common build artifacts, dependency directories, and generated files from Prettier formatting. The centralization aligns with the PR objective of moving formatting configurations to the root level, making maintenance easier.

prettier.config.mjs (1)

1-4: Clean configuration with proper plugin

The configuration properly includes the prettier-plugin-organize-imports plugin which will automatically organize imports in files. The TODO comment acknowledges the plan to add prettier-plugin-tailwindcss in the future, which aligns with the PR objective.

Keep in mind that adding the Tailwind plugin later will likely require significant formatting changes across the codebase as mentioned in your TODO comment.

packages/server/package.json (2)

38-38: Successfully removed linting and formatting scripts

The package.json has been streamlined by removing all linting and formatting-related scripts, keeping only the essential dev script. This aligns perfectly with the PR objective of centralizing these configurations at the root level.


40-51: Properly removed formatting and linting dependencies

The devDependencies have been correctly streamlined to remove all ESLint, Prettier, and TypeScript ESLint-related packages. This reinforces the centralization of tooling at the root level and reduces package-level maintenance overhead.

eslint.config.mjs (3)

20-25: Good package-specific configuration for create-llama

You've properly set up specific linting rules for the create-llama package, preserving the essential rules from its previous configuration. This ensures consistent code quality while centralizing the configuration.


27-31: Server package configuration includes proper TypeScript rules

The configuration for server packages correctly applies the TypeScript ESLint recommended rules. The TODO comment acknowledges the plan to eventually unify the rules across packages, which is good documentation of technical debt.


43-47: Appropriate ignore patterns

The ignore patterns have been correctly extended to include additional directories (python/** and **/e2e/cache/**) that should be excluded from linting. This prevents unnecessary linting of non-source code files.

package.json (3)

2-17: Meta configuration looks correct
The root-level fields (name, version, private, description, keywords, repository, license, and workspaces) are well structured and appropriately scoped for a monorepo setup.


25-30: Verify Husky hook migration and release scripts
You’ve consolidated prepare, new-snapshot, new-version, and release* under the root. Please confirm that:

  1. The .husky/ directory is present at the repo root and Husky hooks are installed correctly.
  2. Running pnpm run new-snapshot/new-version/release behaves as expected across all workspaces.

51-54: Confirm Node.js engine requirement
You’ve set "node": ">=16.14.0". Next.js 15 and some modern packages often recommend Node.js 18+. Please verify that all workspace packages (e.g., Next.js components) function correctly on Node 16, or consider bumping the engine to match upstream requirements.

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: 1

🧹 Nitpick comments (3)
packages/create-llama/e2e/utils.ts (1)

70-79: Logic improvement and variable declaration enhancement.

The changes here properly fix the conditional logic for handling different data source types. By using separate conditions for --web-source and --db-source, the code now correctly processes each data source type independently.

While changing from let to const is generally good practice, note that the array is still being mutated through push() operations. Consider using immutable array operations if you want to fully embrace functional programming principles.

- const dataSourceArgs = [];
- if (dataSource.includes("--web-source")) {
+ const dataSourceArgs = dataSource.includes("--web-source") 
+   ? ["--web-source", dataSource.split(" ")[1]] 
+   : dataSource.includes("--db-source")
+     ? ["--db-source", dataSource.split(" ")[1]]
+     : [dataSource];

This alternative approach would remove the need for mutation, but the current implementation is also valid and clear.

packages/create-llama/templates/types/streaming/nextjs/app/components/ui/chat/tools/artifact.tsx (1)

288-288: Consider using Next.js Image component.

While the ESLint directive disabling the @next/next/no-img-element rule has been removed, the code still uses a standard HTML img element instead of Next.js's optimized Image component.

Consider replacing the HTML img element with Next.js's Image component for better performance and optimization:

- <img src={url.url} alt={url.filename} className="my-4 w-1/2" />
+ <Image src={url.url} alt={url.filename} width={500} height={300} className="my-4 w-1/2" />

Don't forget to import the Image component:

+ import Image from "next/image";
packages/create-llama/helpers/python.ts (1)

27-35: Consider refactoring the function to use an options object

The ESLint directive was added to bypass the max-params rule, which is now being enforced by the consolidated linting configuration. While this approach works, having 6 parameters makes the function harder to maintain and use correctly.

Consider refactoring the function to use a configuration object pattern:

-const getAdditionalDependencies = (
-  modelConfig: ModelConfig,
-  vectorDb?: TemplateVectorDB,
-  dataSources?: TemplateDataSource[],
-  tools?: Tool[],
-  templateType?: TemplateType,
-  observability?: TemplateObservability,
-  // eslint-disable-next-line max-params
-) => {
+interface DependencyOptions {
+  modelConfig: ModelConfig;
+  vectorDb?: TemplateVectorDB;
+  dataSources?: TemplateDataSource[];
+  tools?: Tool[];
+  templateType?: TemplateType;
+  observability?: TemplateObservability;
+}
+
+const getAdditionalDependencies = ({
+  modelConfig,
+  vectorDb,
+  dataSources,
+  tools,
+  templateType,
+  observability,
+}: DependencyOptions) => {

You would also need to update the function call at line 670:

-  const addOnDependencies = getAdditionalDependencies(
-    modelConfig,
-    vectorDb,
-    dataSources,
-    tools,
-    template,
-  );
+  const addOnDependencies = getAdditionalDependencies({
+    modelConfig,
+    vectorDb,
+    dataSources,
+    tools,
+    templateType: template,
+    observability,
+  });

This approach improves readability, maintainability, and avoids the need for ESLint exceptions.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eec050e and 6668fa2.

📒 Files selected for processing (31)
  • eslint.config.mjs (2 hunks)
  • packages/create-llama/create-app.ts (0 hunks)
  • packages/create-llama/e2e/shared/llamaindexserver_template.spec.ts (0 hunks)
  • packages/create-llama/e2e/shared/reflex_template.spec.ts (0 hunks)
  • packages/create-llama/e2e/shared/streaming_template.spec.ts (0 hunks)
  • packages/create-llama/e2e/utils.ts (1 hunks)
  • packages/create-llama/helpers/copy.ts (0 hunks)
  • packages/create-llama/helpers/env-variables.ts (2 hunks)
  • packages/create-llama/helpers/git.ts (0 hunks)
  • packages/create-llama/helpers/install.ts (0 hunks)
  • packages/create-llama/helpers/is-folder-empty.ts (0 hunks)
  • packages/create-llama/helpers/poetry.ts (0 hunks)
  • packages/create-llama/helpers/providers/index.ts (1 hunks)
  • packages/create-llama/helpers/python.ts (1 hunks)
  • packages/create-llama/helpers/validate-pkg.ts (0 hunks)
  • packages/create-llama/index.ts (0 hunks)
  • packages/create-llama/playwright.config.ts (0 hunks)
  • packages/create-llama/templates/components/engines/typescript/agent/tools/interpreter.ts (1 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/astra/generate.ts (0 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/astra/index.ts (0 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/chroma/generate.ts (0 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/chroma/index.ts (0 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/milvus/generate.ts (0 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/mongo/generate.ts (0 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/mongo/index.ts (0 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/pinecone/generate.ts (0 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/pinecone/index.ts (0 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/qdrant/generate.ts (0 hunks)
  • packages/create-llama/templates/components/vectordbs/typescript/weaviate/generate.ts (0 hunks)
  • packages/create-llama/templates/types/streaming/nextjs/app/components/ui/chat/tools/artifact.tsx (1 hunks)
  • packages/create-llama/templates/types/streaming/nextjs/app/components/ui/chat/tools/chat-tools.tsx (1 hunks)
💤 Files with no reviewable changes (23)
  • packages/create-llama/templates/components/vectordbs/typescript/pinecone/index.ts
  • packages/create-llama/templates/components/vectordbs/typescript/mongo/index.ts
  • packages/create-llama/templates/components/vectordbs/typescript/milvus/generate.ts
  • packages/create-llama/templates/components/vectordbs/typescript/pinecone/generate.ts
  • packages/create-llama/templates/components/vectordbs/typescript/mongo/generate.ts
  • packages/create-llama/templates/components/vectordbs/typescript/astra/generate.ts
  • packages/create-llama/templates/components/vectordbs/typescript/weaviate/generate.ts
  • packages/create-llama/templates/components/vectordbs/typescript/astra/index.ts
  • packages/create-llama/helpers/poetry.ts
  • packages/create-llama/playwright.config.ts
  • packages/create-llama/index.ts
  • packages/create-llama/helpers/install.ts
  • packages/create-llama/templates/components/vectordbs/typescript/qdrant/generate.ts
  • packages/create-llama/templates/components/vectordbs/typescript/chroma/generate.ts
  • packages/create-llama/e2e/shared/streaming_template.spec.ts
  • packages/create-llama/e2e/shared/llamaindexserver_template.spec.ts
  • packages/create-llama/helpers/is-folder-empty.ts
  • packages/create-llama/helpers/copy.ts
  • packages/create-llama/e2e/shared/reflex_template.spec.ts
  • packages/create-llama/helpers/validate-pkg.ts
  • packages/create-llama/create-app.ts
  • packages/create-llama/helpers/git.ts
  • packages/create-llama/templates/components/vectordbs/typescript/chroma/index.ts
✅ Files skipped from review due to trivial changes (3)
  • packages/create-llama/templates/components/engines/typescript/agent/tools/interpreter.ts
  • packages/create-llama/templates/types/streaming/nextjs/app/components/ui/chat/tools/chat-tools.tsx
  • packages/create-llama/helpers/providers/index.ts
🚧 Files skipped from review as they are similar to previous changes (1)
  • eslint.config.mjs
⏰ Context from checks skipped due to timeout of 90000ms (27)
  • GitHub Check: typescript (22, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: typescript (22, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: typescript (22, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: typescript (22, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (22, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: typescript (22, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: typescript (22, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (22, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: typescript (22, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --llamacloud)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --example-file)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --no-files)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --llamacloud)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --example-file)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --no-files)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --llamacloud)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --example-file)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --no-files)
🔇 Additional comments (1)
packages/create-llama/helpers/env-variables.ts (1)

184-209: Improve code structure with explicit block scoping

The addition of curly braces around the "chroma" case in the switch statement improves readability and prevents variable leakage between cases. This is a good practice that helps clearly delineate the scope of the case block.

@thucpn thucpn requested a review from marcusschiesser April 29, 2025 09:11
@thucpn thucpn merged commit 1357c42 into main Apr 29, 2025
33 checks passed
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.

2 participants