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

feat(URL): Share link with search parameters #173

Draft
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

Henry8192
Copy link
Collaborator

@Henry8192 Henry8192 commented Jan 27, 2025

Description

Validation performed

Summary by CodeRabbit

Release Notes

  • New Features

    • Added a share button in the search tab panel to copy a permalink with current search parameters
    • Enhanced URL context to support case sensitivity, regex, and query string parameters
  • Improvements

    • Improved state management for file loading and query handling
    • Added dynamic query triggering based on URL parameters
  • Technical Updates

    • Expanded URL search parameters to provide more detailed search configurations

The update introduces more flexible search functionality and improved user experience for sharing search settings.

Copy link

coderabbitai bot commented Jan 27, 2025

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The pull request introduces enhanced functionality for search parameter management across multiple components. The changes primarily focus on expanding the URL context to include case sensitivity, regex options, and query string parameters. A new sharing feature is added to the SearchTabPanel, allowing users to copy a permalink with current search parameters. The modifications involve updates to the UrlContextProvider, StateContextProvider, and SearchTabPanel components, creating a more robust mechanism for handling and sharing search configurations.

Changes

File Change Summary
src/typings/url.ts Added new enum entries for IS_CASE_SENSITIVE, IS_REGEX, and QUERY_STRING; Updated UrlSearchParams interface to include new parameters
src/contexts/UrlContextProvider.tsx Extended URL_SEARCH_PARAMS_DEFAULT with new parameters; Modified getWindowUrlSearchParams to retrieve new search parameters
src/contexts/StateContextProvider.tsx Added isFileLoaded state; Expanded context to include isCaseSensitive, isRegex, and queryString; Updated loadFile and added useEffect for query handling
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx Added share button; Implemented handleShareButtonClick; Updated queryString initialization and textarea binding

Sequence Diagram

sequenceDiagram
    participant User
    participant SearchTabPanel
    participant UrlContext
    participant Clipboard

    User->>SearchTabPanel: Click Share Button
    SearchTabPanel->>UrlContext: Retrieve current search params
    UrlContext-->>SearchTabPanel: Return params
    SearchTabPanel->>Clipboard: Copy permalink
    Clipboard-->>User: Confirmation of copied URL
Loading

Possibly Related PRs

Suggested Reviewers

  • junhaoliao

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

@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 (2)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (1)

80-86: Consider omitting the empty object parameter.

The empty object passed as hashParamsUpdates is unnecessary.

 const handleShareButtonClick = () => {
     copyPermalinkToClipboard({
         queryString: queryString,
         isCaseSensitive: getIsCaseSensitive(queryOptions),
         isRegex: getIsRegex(queryOptions),
-    }, {});
+    });
 };
src/contexts/StateContextProvider.tsx (1)

459-468: Simplify the search parameter condition.

The condition is complex and could be simplified. Also, consider moving the URL parameter reset to a cleanup function.

 useEffect(() => {
-    if (URL_SEARCH_PARAMS_DEFAULT.queryString !== queryString && URL_SEARCH_PARAMS_DEFAULT.isCaseSensitive !== isCaseSensitive && URL_SEARCH_PARAMS_DEFAULT.isRegex !== isRegex) {
+    const hasSearchParams = queryString !== URL_SEARCH_PARAMS_DEFAULT.queryString ||
+        isCaseSensitive !== URL_SEARCH_PARAMS_DEFAULT.isCaseSensitive ||
+        isRegex !== URL_SEARCH_PARAMS_DEFAULT.isRegex;
+    
+    if (hasSearchParams) {
         startQuery({queryString, isCaseSensitive, isRegex});
     }
-    updateWindowUrlSearchParams({
-        [SEARCH_PARAM_NAMES.QUERY_STRING]: URL_SEARCH_PARAMS_DEFAULT.queryString,
-        [SEARCH_PARAM_NAMES.IS_CASE_SENSITIVE]: URL_SEARCH_PARAMS_DEFAULT.isCaseSensitive,
-        [SEARCH_PARAM_NAMES.IS_REGEX]: URL_SEARCH_PARAMS_DEFAULT.isRegex,
-    });
+    
+    return () => {
+        updateWindowUrlSearchParams({
+            [SEARCH_PARAM_NAMES.QUERY_STRING]: URL_SEARCH_PARAMS_DEFAULT.queryString,
+            [SEARCH_PARAM_NAMES.IS_CASE_SENSITIVE]: URL_SEARCH_PARAMS_DEFAULT.isCaseSensitive,
+            [SEARCH_PARAM_NAMES.IS_REGEX]: URL_SEARCH_PARAMS_DEFAULT.isRegex,
+        });
+    };
 }, [isFileLoaded]);
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 393f8f8 and d398cee.

📒 Files selected for processing (4)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (4 hunks)
  • src/contexts/StateContextProvider.tsx (4 hunks)
  • src/contexts/UrlContextProvider.tsx (2 hunks)
  • src/typings/url.ts (2 hunks)
🧰 Additional context used
📓 Path-based instructions (4)
src/contexts/UrlContextProvider.tsx (1)

Pattern **/*.{cpp,hpp,java,js,jsx,ts,tsx}: - Prefer false == <expression> rather than !<expression>.

src/typings/url.ts (1)

Pattern **/*.{cpp,hpp,java,js,jsx,ts,tsx}: - Prefer false == <expression> rather than !<expression>.

src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (1)

Pattern **/*.{cpp,hpp,java,js,jsx,ts,tsx}: - Prefer false == <expression> rather than !<expression>.

src/contexts/StateContextProvider.tsx (1)

Pattern **/*.{cpp,hpp,java,js,jsx,ts,tsx}: - Prefer false == <expression> rather than !<expression>.

🔇 Additional comments (9)
src/typings/url.ts (2)

6-8: LGTM! The new search parameter names are well-defined.

The added enum values follow consistent naming conventions and use appropriate camelCase for URL parameters.


17-19: LGTM! The interface properties are well-typed.

The added properties use appropriate types and maintain type safety through computed property names.

src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (3)

16-16: LGTM! The imports support the new sharing functionality.

The added imports are necessary and well-organized.

Also applies to: 21-24


72-72: LGTM! The URL context integration is well-implemented.

The context usage and state initialization follow React best practices with proper null handling.

Also applies to: 75-75


131-136: LGTM! The share button UI is well-integrated.

The button follows consistent patterns and provides clear user feedback through the tooltip.

src/contexts/UrlContextProvider.tsx (1)

27-29: LGTM! The default parameters are consistently defined.

The new search parameters follow the established pattern and ordering.

src/contexts/StateContextProvider.tsx (3)

249-249: LGTM! The URL context usage is complete.

All necessary search parameters are extracted in a consistent order.


254-255: LGTM! The file loading state is well-managed.

The state is properly initialized and updated in the file info handler.

Also applies to: 309-309


424-425: LGTM! The query state reset is appropriate.

Query results and progress are properly reset when loading a new file.

src/contexts/UrlContextProvider.tsx Show resolved Hide resolved
@junhaoliao
Copy link
Member

(no rush; whenever you have time; preferably after your vacation)
hey @Henry8192 , if the PR is ready for review, can you resolve all conflicts and fill out the PR description? then please request a review from me and we can discuss accordingly.

Copy link
Member

@junhaoliao junhaoliao left a comment

Choose a reason for hiding this comment

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

great job. the changes are mostly clean but i think we can make some structural improvements.
please do merge yscope/main into your branch before making further changes, to avoid more conflicts.

src/contexts/StateContextProvider.tsx Outdated Show resolved Hide resolved
src/contexts/StateContextProvider.tsx Outdated Show resolved Hide resolved
Comment on lines 460 to 468
if (URL_SEARCH_PARAMS_DEFAULT.queryString !== queryString && URL_SEARCH_PARAMS_DEFAULT.isCaseSensitive !== isCaseSensitive && URL_SEARCH_PARAMS_DEFAULT.isRegex !== isRegex) {
startQuery({queryString, isCaseSensitive, isRegex});
}
updateWindowUrlSearchParams({
[SEARCH_PARAM_NAMES.QUERY_STRING]: URL_SEARCH_PARAMS_DEFAULT.queryString,
[SEARCH_PARAM_NAMES.IS_CASE_SENSITIVE]: URL_SEARCH_PARAMS_DEFAULT.isCaseSensitive,
[SEARCH_PARAM_NAMES.IS_REGEX]: URL_SEARCH_PARAMS_DEFAULT.isRegex,
});
}, [isFileLoaded]);
Copy link
Member

Choose a reason for hiding this comment

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

I feel some of these handlings shall be done in the UrlContextProvider instead:

  1. Instead of expecting queryString, isCaseSensitive and isRegex from the URL search parameters, can we expect queryParams.queryString, queryParams.isCaseSensitive and queryParams.isRegex instead?
  2. Shall we assume both queryParams.isCaseSensitive and queryParams.isRegex are false when they are absent in the URL? i.e., shall we consider making those parameters optional?
  3. I think the onus to clear the query parameters shall be on the UrlContextProvider rather than the StateContextProvider.
  4. Then instead of exposing state variables queryString, isCaseSensitive and isRegex directly from the UrlContextProvider, can we expose a single object queryParams? That way in the StateContextProvider code, we can simply check if queryParams is null.

@Henry8192 Henry8192 marked this pull request as draft January 29, 2025 13:11
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