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 new public api function BackToQueryResults for chaning the query list back to query results list #3087

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

Jack251970
Copy link
Contributor

Add new public api function for chaning the query list back to query results list.

As existing api function ReQuery(bool reselect = true) function when selected item is from query results only, this api is for making this function work when selected item is from context menu or history.

E.g.: In one context menu result, you need to invoke a function to return to query list and refresh the list. And you need to call BackToQueryResults(); before calling ReQuery();.

@prlabeler prlabeler bot added the enhancement New feature or request label Nov 21, 2024
Copy link

gitstream-cm bot commented Nov 21, 2024

🥷 Code experts: onesounds

onesounds has most 👩‍💻 activity in the files.
jjw24 has most 🧠 knowledge in the files.

See details

Flow.Launcher.Plugin/Interfaces/IPublicAPI.cs

Activity based on git-commit:

onesounds
NOV
OCT
SEP
AUG
JUL
JUN

Knowledge based on git-blame:
jjw24: 20%

Flow.Launcher/PublicAPIInstance.cs

Activity based on git-commit:

onesounds
NOV
OCT
SEP
AUG
JUL
JUN 33 additions & 14 deletions

Knowledge based on git-blame:
jjw24: 17%

Flow.Launcher/ViewModel/MainViewModel.cs

Activity based on git-commit:

onesounds
NOV
OCT
SEP
AUG
JUL
JUN 3 additions & 3 deletions

Knowledge based on git-blame:
jjw24: 2%

To learn more about /:\ gitStream - Visit our Docs

Copy link

gitstream-cm bot commented Nov 21, 2024

Be a legend 🏆 by adding a before and after screenshot of the changes you made, especially if they are around UI/UX.

Copy link

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

Copy link
Contributor

coderabbitai bot commented Nov 21, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request involve the addition of a new method, BackToQueryResults, to the IPublicAPI interface, the PublicAPIInstance class, and the MainViewModel class within the Flow.Launcher namespace. This method allows users to navigate back to query results from context menus or history. Additionally, the ReQuery method's documentation has been updated to clarify its intended use case. These modifications enhance the interface and control flow without altering existing functionalities.

Changes

File Path Change Summary
Flow.Launcher.Plugin/Interfaces/IPublicAPI.cs - Added method: public void BackToQueryResults()
- Updated documentation for ReQuery(bool reselect = true)
Flow.Launcher/PublicAPIInstance.cs - Added method: public void BackToQueryResults()
Flow.Launcher/ViewModel/MainViewModel.cs - Added method: public void BackToQueryResults()
- Minor change in using directives

Poem

In the world of queries, hop and play,
A new path opens, bright as day.
Back to results, with a joyful cheer,
Navigation made easy, no need to fear!
So let us leap, with a twitch of our nose,
To query results, where the knowledge flows! 🐰✨


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

🧹 Outside diff range and nitpick comments (3)
Flow.Launcher.Plugin/Interfaces/IPublicAPI.cs (1)

297-300: Enhance ReQuery method documentation

While the added clarification is helpful, consider expanding the documentation to:

  1. Explain what happens if called when selected item is not from query results
  2. Add @param documentation for the reselect parameter explaining its behavior
 /// <summary>
 /// Reloads the query.
 /// This method should run when selected item is from query results.
+/// Note: Behavior is undefined when called with selected items from context menu or history.
 /// </summary>
+/// <param name="reselect">If true, selects the first result after reload. If false, attempts to maintain the current selection.</param>
 public void ReQuery(bool reselect = true);
Flow.Launcher/ViewModel/MainViewModel.cs (2)

487-493: Add XML documentation for the public API method.

Since this is a public API method, it should include XML documentation to describe its purpose, behavior, and usage scenarios.

+/// <summary>
+/// Navigates back to the query results list from context menu or history.
+/// This method should be called before invoking ReQuery() when the selected item
+/// is from a context menu or history to ensure correct functionality.
+/// </summary>
 public void BackToQueryResults()
 {
     if (!SelectedIsFromQueryResults())
     {
         SelectedResults = Results;
     }
 }

487-493: Add unit tests for the new API method.

Consider adding unit tests to verify:

  1. Navigation back to query results from context menu
  2. Navigation back to query results from history
  3. No-op when already in query results

Would you like me to help generate the unit test cases?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7e9ed8e and 6df0837.

📒 Files selected for processing (3)
  • Flow.Launcher.Plugin/Interfaces/IPublicAPI.cs (1 hunks)
  • Flow.Launcher/PublicAPIInstance.cs (1 hunks)
  • Flow.Launcher/ViewModel/MainViewModel.cs (2 hunks)
🔇 Additional comments (4)
Flow.Launcher/PublicAPIInstance.cs (2)

321-322: LGTM - Method placement and implementation are consistent.

The new method follows the established patterns in the codebase:

  • Placed in the correct region (Public API)
  • Located next to related functionality (ReQuery)
  • Implementation matches the delegation pattern used by other API methods

321-322: Consider adding error handling or state validation.

The method delegates directly to _mainVM.BackToQueryResults() without any checks. Consider validating the current state or handling potential errors, especially since this method is part of the public API.

Let's check how other view model methods handle similar scenarios:

Flow.Launcher.Plugin/Interfaces/IPublicAPI.cs (1)

302-306: 🛠️ Refactor suggestion

Enhance BackToQueryResults documentation and verify implementation

The new method addresses the workflow gap, but its documentation should be expanded to provide clearer guidance for plugin developers.

 /// <summary>
 /// Back to the query results.
 /// This method should run when selected item is from context menu or history.
+/// <remarks>
+/// Use this method to return to the query results list before calling ReQuery when:
+/// - User has selected an item from a context menu
+/// - User has selected an item from history
+/// 
+/// Example workflow:
+/// ```csharp
+/// // When needing to refresh results after context menu action
+/// BackToQueryResults();
+/// ReQuery();
+/// ```
+/// </remarks>
 /// </summary>
 public void BackToQueryResults();

Let's verify the implementation details:

Flow.Launcher/ViewModel/MainViewModel.cs (1)

487-493: LGTM! Well integrated with existing navigation logic.

The implementation follows established patterns and correctly integrates with the existing navigation flow between different result views.

Flow.Launcher/PublicAPIInstance.cs Show resolved Hide resolved
Copy link
Member

@jjw24 jjw24 left a comment

Choose a reason for hiding this comment

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

LGTM, let's hold off merging until we do v1.20.0 release.

@jjw24 jjw24 added this to the Future milestone Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants