Breaking change: move semdex config to root config and rename "WEAVIATE_ENABLED" to "SEMDEX_ENABLED"

Southclaws commented 1 week ago

Exposing capabilities to frontends to selectively reveal features.

vercel[bot] commented 1 week ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
storyden	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 8, 2024 6:48pm

1 Skipped Deployment

coderabbitai[bot] commented 1 week ago

[!WARNING]

Rate limit exceeded

@Southclaws has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 18 minutes and 54 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](https://coderabbit.ai/docs/faq) for further information.

📥 Commits
Reviewing files that changed from the base of the PR and between e40c24ca97d59c24fa22ba97b928359d1c8c8da8 and 311e81eba0048c09303e8c3dcd555bba6e4849d5.

📝 Walkthrough

## Walkthrough The changes in this pull request introduce a new configuration parameter to the `newSemdexer` function, allowing it to access settings from a `config.Config` object. The `Config` struct has been updated to include several new fields for environment variable configuration. Additionally, the `weaviate.go` file has been modified to streamline the Weaviate client configuration process by removing the previous `Configuration` struct and directly utilizing the `config.Config` object. ## Changes | File Path | Change Summary | |---------------------------------------|-----------------------------------------------------------------------------------------------------| | app/services/semdex/semdexer/semdexer.go | Updated `newSemdexer` to accept `cfg config.Config`, modifying instantiation logic based on `cfg.SemdexEnabled`. | | internal/config/config.go | Added new fields to `Config`: `SemdexEnabled`, `WeaviateURL`, `WeaviateToken`, `WeaviateClassName`, `OpenAIKey`, each with corresponding `envconfig` tags. | | internal/infrastructure/weaviate/weaviate.go | Removed `Configuration` struct; updated `newWeaviateClient` to accept `cfg config.Config`, altering field references to match the new configuration structure. | | app/services/services.go | Added import for `instance_info` and provisioned `instance_info.New` in `Build` function. | | app/services/system/instance_info/capabilities.go | Introduced `capabilityEnum` type and constants for capabilities. | | app/services/system/instance_info/info.go | Added `Provider` struct and methods for managing settings and capabilities. | | app/services/system/instance_info/instance_info_enum_gen.go | Defined `Capability` type and associated methods for capabilities management. | | app/transports/http/bindings/info.go | Updated `Info` struct to use `*instance_info.Provider` and modified related methods. | | web/src/api/openapi-schema/index.ts | Added exports for `instanceCapability` and `instanceCapabilityList`. | | web/src/api/openapi-schema/info.ts | Added `capabilities` property to the `Info` interface. | | web/src/api/openapi-schema/instanceCapability.ts | Defined `InstanceCapability` type and constant. | | web/src/api/openapi-schema/instanceCapabilityList.ts | Defined `InstanceCapabilityList` type as an array of `InstanceCapability`. | ## Poem > In the garden of code, we hop and play, > New configs sprout, brightening the day. > Semdex now dances with settings so neat, > Weaviate whispers, "Oh, what a treat!" > With every change, our paths intertwine, > Hopping through code, oh, how we shine! 🐇✨

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

Southclaws / storyden

Breaking change: move semdex config to root config and rename "WEAVIATE_ENABLED" to "SEMDEX_ENABLED" #281

Rate limit exceeded