Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Add possibility to customize request view mappings #185

Merged
merged 1 commit into from
Aug 1, 2024

Conversation

yngwi
Copy link
Contributor

@yngwi yngwi commented Aug 1, 2024

Closes issue #184 by adding a mappings section to the _HURL_GLOBAL_CONFIG table and using the individual mappings when registering mappings for the split and popup response views.

Note: vim.tbl_extend has been replaced with vim.tbl_deep_extend when merging the default and user provided config tables to ensure also partial custom user mappings are possible. This also affects other settings. I hope this is OK.

Summary by CodeRabbit

  • New Features

    • Introduced customizable keyboard shortcuts for managing response popups in Neovim, including shortcuts for closing popups and navigating between them.
  • Documentation

    • Updated documentation to reflect new configuration options and provide clearer guidance on customizing key mappings for the hurl.nvim plugin.
  • Refactor

    • Enhanced flexibility in handling key mappings by using a centralized configuration object, improving maintainability and configurability of popup behavior.

Copy link

codesandbox bot commented Aug 1, 2024

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

Copy link

changeset-bot bot commented Aug 1, 2024

⚠️ No Changeset found

Latest commit: 8d6a369

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.

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

ellipsis-dev bot commented Aug 1, 2024

Your free trial has expired. To keep using Ellipsis, sign up at https://app.ellipsis.dev for $20/seat/month or reach us at [email protected]

Copy link
Contributor

coderabbitai bot commented Aug 1, 2024

Walkthrough

This update enhances the Neovim configuration for the hurl.nvim plugin by introducing a centralized mappings table. This new feature defines intuitive keyboard shortcuts for managing response popups and split views, improving user interaction. Key actions like closing popups or navigating between panels are now customizable, streamlining the overall user experience and making the plugin more adaptable.

Changes

Files Change Summary
README.md, doc/hurl.nvim.txt Added a new mappings section for defining default key bindings for closing and navigating response popups. Updated documentation for customization.
lua/hurl/init.lua Introduced a mappings table in default_config for keyboard shortcuts. Changed configuration merging from vim.tbl_extend to vim.tbl_deep_extend.
lua/hurl/popup.lua, lua/hurl/split.lua Refactored key mappings to use _HURL_GLOBAL_CONFIG for flexibility and configurability, enhancing maintainability of popup controls.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant HurlPopup
    participant GlobalConfig

    User->>HurlPopup: Press 'q'
    HurlPopup->>GlobalConfig: Check mapping for close
    GlobalConfig-->>HurlPopup: Return close mapping
    HurlPopup->>User: Close the popup
Loading

🐰 In a world of keys, so bright and fine,
The rabbit hops, with joy in line.
Mappings now dance, a customizable spree,
Closing and navigating, oh what glee!
With each little press, a wish comes true,
Hurl's magic unfolds, just for you! 🌟


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

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: 0

Outside diff range, codebase verification and nitpick comments (2)
doc/hurl.nvim.txt (2)

346-355: Fix punctuation issues.

The list items have loose punctuation marks. Ensure consistent punctuation for better readability.

- - `q`: Close the current popup window or split.
- - `<C-n>`: Switch to the next popup window.
- - `<C-p>`: Switch to the previous popup window.
+ - `q`: Close the current popup window or split.
+ - `<C-n>`: Switch to the next popup window.
+ - `<C-p>`: Switch to the previous popup window.
Tools
LanguageTool

[uncategorized] ~346-~346: Loose punctuation mark.
Context: ...ings to streamline your workflow: - q: Close the current popup window or split...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~347-~347: Loose punctuation mark.
Context: ...current popup window or split. - <C-n>: Switch to the next popup window. - `<C-...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~348-~348: Loose punctuation mark.
Context: ...itch to the next popup window. - <C-p>: Switch to the previous popup window. T...

(UNLIKELY_OPENING_PUNCTUATION)


437-439: Inconsistent key mappings detected.

The custom key mapping for the close action in the example configuration (<C-c>) is inconsistent with the default mapping ('q') documented earlier.

  • lua/hurl/init.lua
    • close = 'q'
  • doc/hurl.nvim.txt (lines 437-439)
    • close = '<C-c>'

Please ensure that the key mappings in the example configuration are consistent with the default mappings.

Analysis chain

Ensure consistency in key mappings.

The custom key mappings in the example configuration should be consistent with the default mappings documented earlier.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify consistency in key mappings.

# Test: Search for the key mappings in the configuration. Expect: Consistent mappings.
rg --type lua -A 5 $'mappings = {'

Length of output: 123


Script:

#!/bin/bash
# Description: Verify consistency in key mappings.

# Test: Search for the key mappings in the configuration. Expect: Consistent mappings.
rg --type lua -A 5 $'mappings = \\{'

Length of output: 365

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0143872 and 8d6a369.

Files selected for processing (5)
  • README.md (1 hunks)
  • doc/hurl.nvim.txt (4 hunks)
  • lua/hurl/init.lua (2 hunks)
  • lua/hurl/popup.lua (1 hunks)
  • lua/hurl/split.lua (1 hunks)
Additional context used
LanguageTool
doc/hurl.nvim.txt

[uncategorized] ~346-~346: Loose punctuation mark.
Context: ...ings to streamline your workflow: - q: Close the current popup window or split...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~347-~347: Loose punctuation mark.
Context: ...current popup window or split. - <C-n>: Switch to the next popup window. - `<C-...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~348-~348: Loose punctuation mark.
Context: ...itch to the next popup window. - <C-p>: Switch to the previous popup window. T...

(UNLIKELY_OPENING_PUNCTUATION)

Additional comments not posted (10)
lua/hurl/init.lua (2)

48-53: LGTM! Adding the mappings table enhances user customization.

The addition of the mappings table allows users to define their own key mappings for response views, which improves the user experience.


69-69: LGTM! Changing to vim.tbl_deep_extend improves configuration merging.

Using vim.tbl_deep_extend ensures that nested tables are merged correctly, preserving existing nested configuration options while updating them with new values.

lua/hurl/split.lua (1)

84-84: LGTM! Using _HURL_GLOBAL_CONFIG.mappings.close enhances configurability.

Changing the key mapping for closing a split window to use _HURL_GLOBAL_CONFIG.mappings.close allows users to customize this key mapping, improving flexibility and user experience.

lua/hurl/popup.lua (4)

65-65: LGTM! Using _HURL_GLOBAL_CONFIG.mappings.close enhances configurability.

Changing the key mapping for closing the top popup window to use _HURL_GLOBAL_CONFIG.mappings.close allows users to customize this key mapping, improving flexibility and user experience.


68-68: LGTM! Using _HURL_GLOBAL_CONFIG.mappings.close enhances configurability.

Changing the key mapping for closing the bottom popup window to use _HURL_GLOBAL_CONFIG.mappings.close allows users to customize this key mapping, improving flexibility and user experience.


73-73: LGTM! Using _HURL_GLOBAL_CONFIG.mappings.next_panel enhances configurability.

Changing the key mapping for navigating to the next popup window to use _HURL_GLOBAL_CONFIG.mappings.next_panel allows users to customize this key mapping, improving flexibility and user experience.


80-83: LGTM! Using _HURL_GLOBAL_CONFIG.mappings.prev_panel enhances configurability.

Changing the key mapping for navigating to the previous popup window to use _HURL_GLOBAL_CONFIG.mappings.prev_panel allows users to customize this key mapping, improving flexibility and user experience.

doc/hurl.nvim.txt (2)

80-85: Document new default key mappings.

The new default key mappings for the response popup or split views are well-documented. This enhances the usability of the plugin by providing clear instructions on how to customize these mappings.


408-412: Document new default key mappings in configuration.

The new default key mappings are clearly documented in the configuration section. This provides users with the necessary information to customize their key mappings effectively.

README.md (1)

63-68: Document new default key mappings.

The new default key mappings for the response popup or split views are well-documented. This enhances the usability of the plugin by providing clear instructions on how to customize these mappings.

Copy link
Owner

@jellydn jellydn left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks @yngwi

@jellydn jellydn merged commit 30c52d7 into jellydn:main Aug 1, 2024
6 checks passed
@jellydn
Copy link
Owner

jellydn commented Aug 1, 2024

@all-contributors add @yngwi for code,doc.

Copy link
Contributor

@jellydn

I've put up a pull request to add @yngwi! 🎉

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