Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

feat: add more event for jsonViewer #5546

Merged
merged 1 commit into from
Feb 17, 2025
Merged

Conversation

mynetfan
Copy link
Collaborator

@mynetfan mynetfan commented Feb 17, 2025

Description

  • 为JsonViewer添加事件支持

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ️ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
  • Run the tests with pnpm test.
  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

  • New Features

    • Enhanced the JSON viewer with additional interactive events (click, key click, value click, toggle, and copy) that provide immediate user feedback.
    • Introduced a preview mode offering improved data display controls, such as array index visibility and copyable content.
    • Updated the sample JSON data to include extended debugging information and log details for richer demonstrations.
  • Refactor

    • Streamlined the component behavior by removing redundant JSON parsing logic for a more consistent user experience.

* 为JsonViewer添加事件支持
Copy link

changeset-bot bot commented Feb 17, 2025

⚠️ No Changeset found

Latest commit: f5d9b1d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

Copy link
Contributor

coderabbitai bot commented Feb 17, 2025

Walkthrough

The changes update the JSON viewer component and its associated types. In the common UI package, new event emissions (click, copied, keyClick, toggle, valueClick) and a handling function (handleClick) are introduced while removing the JSON parsing logic. The types file is updated with new interfaces (JsonViewerAction, JsonViewerToggle, JsonViewerValue) and modifies JsonViewerProps. In the playground, the JSON data constant is now parsed via JSON.parse with an updated structure, and the example view adds new event handler functions with a binding change from v-model to :value to support interactive features.

Changes

File(s) Change Summary
packages/effects/common-ui/src/components/json-viewer/index.vue
packages/effects/common-ui/src/components/json-viewer/types.ts
- Updated JsonViewer event emissions: added "click", "copied", "keyClick", "toggle", and "valueClick"; removed "parseError".
- Added new handleClick function and modified bindProps for new events.
- Updated JsonViewerProps by adding a required value property and removed parseString; introduced interfaces: JsonViewerAction, JsonViewerValue, JsonViewerToggle.
playground/src/views/examples/json-viewer/data.ts
playground/src/views/examples/json-viewer/index.vue
- Modified json2 to be parsed via JSON.parse with an updated JSON structure including a new debug object.
- In the example view: imported new types and the message component, added event handler functions (handleKeyClick, handleValueClick, handleCopied), changed binding from v-model to :value, and added a preview-mode card.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant JV as JsonViewer Component
    participant P as Parent Component
    U->>JV: Clicks on a JSON item
    JV->>JV: Executes handleClick(event)
    JV->>P: Emits "click" & "valueClick" events with parameters
Loading
sequenceDiagram
    participant U as User
    participant PJV as Playground JSON Viewer
    participant M as Message Service
    U->>PJV: Triggers key/value click or copy action
    PJV->>PJV: Calls handleKeyClick / handleValueClick / handleCopied
    PJV->>M: Displays corresponding info or success message
Loading

Possibly related PRs

Suggested reviewers

  • anncwb
  • vince292007

Poem

Oh, how the code hops with delight,
New events dancing in the moonlight.
JSON parsing gracefully stepped aside,
While type safety takes a joyful ride.
A rabbit's cheer in every byte,
Leaping through changes, ever so bright!
🐇

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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>, 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. (Beta)
  • @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 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.

Copy link
Contributor

@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)
playground/src/views/examples/json-viewer/data.ts (1)

29-66: Simplify json2 declaration by removing JSON.parse.

Using JSON.parse at compile time for a static object is unnecessary and could impact performance. Consider using a direct object declaration instead.

-export const json2 = JSON.parse(`
-  {
+export const json2 = {
   "id": "chatcmpl-123",
   // ... rest of the object
-}
-  `);
+};
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7999341 and f5d9b1d.

📒 Files selected for processing (4)
  • packages/effects/common-ui/src/components/json-viewer/index.vue (3 hunks)
  • packages/effects/common-ui/src/components/json-viewer/types.ts (2 hunks)
  • playground/src/views/examples/json-viewer/data.ts (2 hunks)
  • playground/src/views/examples/json-viewer/index.vue (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (7)
  • GitHub Check: Test (windows-latest)
  • GitHub Check: Lint (windows-latest)
  • GitHub Check: Check (windows-latest)
  • GitHub Check: Lint (ubuntu-latest)
  • GitHub Check: Check (ubuntu-latest)
  • GitHub Check: post-update (windows-latest)
  • GitHub Check: post-update (ubuntu-latest)
🔇 Additional comments (5)
packages/effects/common-ui/src/components/json-viewer/types.ts (2)

1-24: LGTM! Props interface is well-defined.

The required value property is properly typed and documented. The removal of parseString aligns with moving parsing responsibility to the consumer.


26-44: LGTM! Event interfaces are well-structured.

The new interfaces (JsonViewerAction, JsonViewerValue, JsonViewerToggle) are properly typed and documented, providing good type safety for event handling.

packages/effects/common-ui/src/components/json-viewer/index.vue (2)

35-41: LGTM! Event emissions are well-typed.

The emit types are properly defined using TypeScript's type system, providing good type safety for event handling.


71-87: LGTM! Event handlers are properly bound.

The computed property correctly binds all event handlers and maintains proper typing.

playground/src/views/examples/json-viewer/index.vue (1)

1-51: LGTM! Example implementation demonstrates proper usage.

The implementation:

  • Properly imports and uses types
  • Implements clear event handlers
  • Demonstrates various JsonViewer features including preview mode
  • Shows good error feedback using message component

@mynetfan mynetfan merged commit b6b97ac into vbenjs:main Feb 17, 2025
14 checks passed
@mynetfan mynetfan deleted the feat/json-viewer branch February 17, 2025 02:41
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant