feat:Rename enumeration values and properties for clarity and consistency

[HavenDV]

Summary by CodeRabbit

• New Features

  • Updated terminology from "ChartsSection" to "Dashboard" for improved clarity in the application.
  • Renamed property from "ChartsSections" to "Dashboards" in the data representation to reflect a focus on dashboard resources.

• Documentation

  • Revised OpenAPI specification to align with new terminology, enhancing clarity for API users.

[coderabbitai]

Walkthrough

The changes involve renaming enumeration values and properties within the codebase to enhance clarity and align with updated terminology. Specifically, the ResourceType enumeration has replaced ChartsSection with Dashboard, and the TaggingsByResourceType class has updated the property ChartsSections to Dashboards. Additionally, the OpenAPI specification has been revised to reflect these naming changes, ensuring consistency across the API documentation.

Changes

Files	Change Summary
src/libs/LangSmith/Generated/LangSmith.Models.ResourceType.g.cs, src/libs/LangSmith/Generated/LangSmith.Models.TaggingsByResourceType.g.cs, src/libs/LangSmith/openapi.yaml	Enumeration value ChartsSection renamed to Dashboard, property ChartsSections changed to Dashboards, and corresponding updates made in OpenAPI specification.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant API
    participant ResourceType

    Client->>API: Request Dashboard data
    API->>ResourceType: Fetch Dashboard resources
    ResourceType-->>API: Return Dashboard resources
    API-->>Client: Respond with Dashboard data

Loading

Poem

🐇 In the code where rabbits hop,
Terms have changed, we won't stop!
From charts to dashboards, clear and bright,
Our code now shines with new delight!
Hopping forward, we embrace the day,
With every change, we leap and play! 🌼

---

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

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

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

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between aa6440e and 9d10184.

Files selected for processing (3)

• src/libs/LangSmith/Generated/LangSmith.Models.ResourceType.g.cs (3 hunks)
• src/libs/LangSmith/Generated/LangSmith.Models.TaggingsByResourceType.g.cs (1 hunks)
• src/libs/LangSmith/openapi.yaml (2 hunks)

Additional comments not posted (6)

src/libs/LangSmith/Generated/LangSmith.Models.ResourceType.g.cs (3)

38-38: LGTM!

The enum value Dashboard correctly replaces ChartsSection.

The code changes are approved.

---

59-59: LGTM!

The ToValueString method correctly maps ResourceType.Dashboard to "dashboard".

The code changes are approved.

---

76-76: LGTM!

The ToEnum method correctly maps the string "dashboard" to ResourceType.Dashboard.

The code changes are approved.

src/libs/LangSmith/Generated/LangSmith.Models.TaggingsByResourceType.g.cs (1)

50-51: LGTM!

The property ChartsSections has been correctly renamed to Dashboards.

The code changes are approved.

src/libs/LangSmith/openapi.yaml (2)

14223-14223: LGTM!

The addition of dashboard to the list of components aligns with the updated terminology.

The code changes are approved.

---

16990-16994: LGTM!

The addition of dashboards as a new property with a title and type aligns with the updated terminology.

The code changes are approved.