Expose ApplicableInputs type

[paluh]

Summary by CodeRabbit

• Refactor
  • Improved export structure for better integration and usage in the application.

[coderabbitai]

Walkthrough

The update in the codebase involves the enhancement of module exports in a TypeScript file. It specifically adds the export of a new item, ApplicableInputs, and modifies the export statement for an existing item, Next. This change likely improves the usability of the module by making additional types available to consumers and streamlining the export structure.

Changes

File Path	Change Summary
packages/language/core/v1/src/next/index.ts	Exported ApplicableInputs and updated export syntax for Next.

🐇✨
To code in the burrow, beneath the moon's glow,
We hop to the rhythm of the keystrokes' flow.
With exports anew, and syntax so bright,
Our module's more useful, oh what a sight! 🌟
🐾

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 76b2336 and b8e94e9.

Files selected for processing (1)

• packages/language/core/v1/src/next/index.ts (1 hunks)

Additional comments: 2

packages/language/core/v1/src/next/index.ts (2)

• 11-11: Export of ApplicableInputs is correct and aligns with the PR objectives.
• 11-13: The Next type is now being exported as a constant, which changes its usage. Ensure that all references to Next throughout the codebase are updated to reflect this change.

[coderabbitai]

Changing Next from a type to a runtime validator using t.type alters its behavior significantly. This change implies that Next can now be used for runtime type checking and validation, which was not possible when it was only a type alias. Confirm that this new behavior is intentional and that all uses of Next are compatible with this change.