Skip to content

Conversation

Yusyuriv
Copy link
Member

@Yusyuriv Yusyuriv commented Nov 3, 2024

Closes #3056.

The button in inputWithFileBtn in SettingsTemplate.yml wasn't working because the button was created and displayed, but it had no click listener attached.

While fixing this, I found out that it's not easily possible to make a dialog that would let the user selected either a file or a folder. It's always either a dialog for selecting only files or a dialog for selecting only folders. Considering this, I also added another type of possible input for JS/Python plugins: inputWithFolderBtn.

I added static imports (using Checkbox = ..., using ComboBox = ..., etc.) because I needed to add the import statement for System.Windows.Forms, but as soon as I added it, it started complaining about ambiguous imports: it didn't know whether it's supposed to use UI components from System.Windows.Controls or from System.Windows.Forms.

Screenshot after I correctly managed to pick a file and a folder after my changes:
image

Plugin's Settings.json file after I ran the Save Settings command in Flow:

{
  "folder": "Z:\\flow-launcher\\Flow.Launcher",
  "file": "Z:\\flow-launcher\\Flow.Launcher\\README.md"
}

If this gets merged, Flow-Launcher/docs#89 also should get merged.

@Yusyuriv Yusyuriv added bug Something isn't working enhancement New feature or request labels Nov 3, 2024
@Yusyuriv Yusyuriv requested a review from taooceros November 3, 2024 06:52
@Yusyuriv Yusyuriv self-assigned this Nov 3, 2024
@github-actions github-actions bot added this to the 1.19.4 milestone Nov 3, 2024

This comment has been minimized.

Copy link
Contributor

coderabbitai bot commented Nov 3, 2024

📝 Walkthrough
<details>
<summary>📝 Walkthrough</summary>

## Walkthrough
The changes in `JsonRPCPluginSettings.cs` enhance the `CreateSettingPanel` method by adding functionality for folder selection alongside file selection. A new case, `"inputWithFolderBtn"`, has been introduced to allow users to select a folder via a `FolderBrowserDialog`. The selected folder path is then assigned to a `TextBox` and stored in the `Settings` dictionary. Additionally, the existing case for file selection has been modified to accommodate this new functionality.

## Changes

| File                                     | Change Summary                                                                                     |
|------------------------------------------|---------------------------------------------------------------------------------------------------|
| Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs | Added folder selection functionality to `CreateSettingPanel` method; modified existing file selection case. |

## Assessment against linked issues

| Objective                                                | Addressed | Explanation                       |
|---------------------------------------------------------|-----------|-----------------------------------|
| Implement click event handler for `inputWithFileBtn` (3056) ||                                   |

## Possibly related PRs
- #2742: Involves user interaction with context menus, which may relate to the folder selection functionality introduced in this PR.
- #2934: Modifies file selection filters, conceptually similar to the folder selection feature added in this PR.

> 🐰 In the meadow, I hop with glee,  
> A folder dialog now waits for thee!  
> With buttons to click and paths to find,  
> Settings are bright, oh so refined!  
> Let's browse and select, oh what a delight,  
> In our plugin's world, everything feels right! 🌼

</details>

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 6604710 and 1bdfc30.

📒 Files selected for processing (1)
  • Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs

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

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 943425b and 6604710.

📒 Files selected for processing (1)
  • Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs (3 hunks)
🔇 Additional comments (3)
Flow.Launcher.Core/Plugin/JsonRPCPluginSettings.cs (3)

7-7: LGTM: Well-structured import declarations.

The explicit imports help prevent ambiguity between WPF and WinForms controls, making the code more maintainable and less prone to compilation errors.

Also applies to: 10-14


234-234: LGTM: Clean addition of folder selection support.

The new case elegantly shares implementation with file selection, following DRY principles.


254-270: Verify the fix addresses the original issue.

The implementation successfully fixes the non-functional "Browse" button issue mentioned in #3056 by properly implementing the click handler. Additionally, it enhances the functionality by supporting folder selection.

Let's verify the usage of these input types across the codebase:

✅ Verification successful

Let me generate additional verification scripts to check for plugin settings usage:

This will help us verify if the implementation aligns with actual plugin settings usage patterns.


Let me generate additional verification scripts to check for plugin settings usage patterns:

This will help verify if the implementation aligns with existing plugin settings patterns and dialog handling.


Based on the verification results, I can now provide the final response:

Implementation successfully fixes the Browse button functionality

The changes correctly implement the file/folder dialog handling in JsonRPCPluginSettings.cs by:

  • Adding proper dialog type switching between FolderBrowserDialog and OpenFileDialog
  • Correctly handling dialog results and path extraction
  • Maintaining proper settings updates

While no direct plugin settings templates were found using these input types, the implementation provides the necessary foundation for plugins to utilize both file and folder selection dialogs through their settings.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for usage of inputWithFileBtn and inputWithFolderBtn in settings templates

# Test: Search for input type usage in yml files
echo "Checking usage in yml files..."
rg -l "inputWithFileBtn|inputWithFolderBtn" --glob "*.yml"

# Test: Search for potential file/folder dialog usage that might need updating
echo "Checking for other file/folder dialog usage..."
rg "OpenFileDialog|FolderBrowserDialog|ShowDialog"

Length of output: 6073


Script:

#!/bin/bash
# Search for plugin settings files and their input type definitions
echo "Checking for plugin settings files..."
fd "plugin.json|settings.json" --type f -x cat {} \;

# Search for any references to the settings implementation
echo "Checking for settings implementation references..."
rg -A 5 "JsonRPCPluginSettings" 

Length of output: 274777


Script:

#!/bin/bash
# Search for plugin settings templates and usage
echo "Checking for plugin settings templates..."
rg -A 5 "inputWithFileBtn|inputWithFolderBtn" --type yaml

# Search for file/folder dialog implementations
echo "Checking for file/folder dialog implementations..."
ast-grep --pattern 'class $_ {
  $$$
  $_(FolderBrowserDialog|OpenFileDialog) $_ {
    $$$
  }
  $$$
}'

Length of output: 369

@Yusyuriv Yusyuriv marked this pull request as ready for review November 3, 2024 07:29
Copy link

github-actions bot commented Nov 3, 2024

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, or 📝 job summary for details.

❌ Errors Count
❌ forbidden-pattern 22
❌ ignored-expect-variant 1
⚠️ non-alpha-in-dictionary 19

See ❌ Event descriptions for more information.

If the flagged items are 🤯 false positives

If items relate to a ...

  • binary file (or some other file you wouldn't want to check at all).

    Please add a file path to the excludes.txt file matching the containing file.

    File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

    ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

  • well-formed pattern.

    If you can write a pattern that would match it,
    try adding it to the patterns.txt file.

    Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

    Note that patterns can't match multiline strings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BUG: inputWithFileBtn in SettingsTemplate.yml: the Browse button doesn't do anything

3 participants