Skip to content

fix: tegg-types publish#212

Merged
killagu merged 1 commit intomasterfrom
fix/types-publish
Apr 17, 2024
Merged

fix: tegg-types publish#212
killagu merged 1 commit intomasterfrom
fix/types-publish

Conversation

@gxkl
Copy link
Contributor

@gxkl gxkl commented Apr 17, 2024

Checklist
  • npm test passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)
Description of change

Summary by CodeRabbit

  • Refactor
    • Improved file inclusion patterns for packaging.
    • Streamlined TypeScript configuration settings.

@coderabbitai
Copy link

coderabbitai bot commented Apr 17, 2024

Walkthrough

This update involves refining the configuration for a TypeScript project within the core/types directory. The changes include enhancing the file inclusion pattern in the package configuration and simplifying the TypeScript compilation settings by removing specific output directory paths.

Changes

File Path Change Summary
.../package.json Updated to use recursive glob patterns in files field.
.../tsconfig.json Removed outDir from compilerOptions.
.../tsconfig.pub.json Removed outDir from compilerOptions.

🐇✨
In the burrow of code, changes are afoot,
A rabbit hops along, leaving prints in the soot.
Glob patterns expand like the meadow in bloom,
OutDirs disappear, giving new features room.
Oh, how the code garden wonderfully grows,
Under the watchful eyes of those who knows. 🌼🌟


Recent Review Details

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 334e13d and 4802c57.
Files selected for processing (3)
  • core/types/package.json (1 hunks)
  • core/types/tsconfig.json (1 hunks)
  • core/types/tsconfig.pub.json (1 hunks)
Files skipped from review due to trivial changes (2)
  • core/types/package.json
  • core/types/tsconfig.pub.json
Additional comments not posted (1)
core/types/tsconfig.json (1)

4-4: Verify the handling of the TypeScript output directory in build scripts.


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>.
    • 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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

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

CodeRabbit Configration 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.

@gxkl gxkl requested review from fengmk2 and killagu April 17, 2024 09:08
Copy link
Contributor

@killagu killagu left a comment

Choose a reason for hiding this comment

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

LGTM

@killagu killagu merged commit 98a4188 into master Apr 17, 2024
@killagu killagu deleted the fix/types-publish branch April 17, 2024 09:51
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