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

Open
wants to merge 20 commits into
base: main
Choose a base branch
from

Conversation

Henry8192
Copy link
Collaborator

@Henry8192 Henry8192 commented Jan 27, 2025

Description

Add support to making queries in the url. Also, a button that generates link to current query is added in SearchTabPanel.

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.
    • Updated query handling to utilize new parameters for improved functionality.

This update introduces more flexible search functionality and enhances the user experience for sharing search settings.

Copy link

coderabbitai bot commented Jan 27, 2025

Walkthrough

The pull request enhances the SearchTabPanel component and related context providers by integrating new functionalities for managing search parameters, including case sensitivity, regex options, and query string parameters. A new sharing feature is introduced, allowing users to copy a permalink with the current search parameters. Key modifications include updates to the UrlContextProvider, StateContextProvider, and SearchTabPanel, improving the overall state management and user experience when handling search configurations.

Changes

File Change Summary
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx Introduced handleShareButtonClick function; updated state initialization for queryString, queryIsCaseSensitive, and queryIsRegex; modified rendering to include a share button.
src/contexts/StateContextProvider.tsx Updated startQuery function signature; removed redundant fileName declaration; reset queryResults before starting a new query.
src/contexts/UrlContextProvider.tsx Added new properties to URL_HASH_PARAMS_DEFAULT; modified functions to handle new hash parameters for case sensitivity and regex.
src/typings/url.ts Updated HASH_PARAM_NAMES enum to include QUERY_IS_CASE_SENSITIVE, QUERY_IS_REGEX, and QUERY_STRING; modified UrlHashParams interface to reflect new parameters.
src/services/LogFileManager/index.ts Renamed parameters in startQuery method from isRegex and isCaseSensitive to queryIsRegex and queryIsCaseSensitive.
src/typings/query.ts Renamed properties in QueryArgs interface from isCaseSensitive to queryIsCaseSensitive and from isRegex to queryIsRegex.
src/typings/worker.ts Updated WorkerReqMap to replace isRegex and isCaseSensitive with queryIsRegex and queryIsCaseSensitive.

Possibly Related PRs

Suggested Reviewers

  • junhaoliao
✨ Finishing Touches
  • 📝 Generate Docstrings

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

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

@Henry8192 Henry8192 marked this pull request as draft January 29, 2025 13:11
@Henry8192 Henry8192 marked this pull request as ready for review February 27, 2025 20:31
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 (3)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (3)

53-53: Consider restructuring to avoid disabling the max-lines-per-function lint rule.
If feasible, reduce the function’s size by extracting logic into smaller helper functions, which can improve maintainability and readability.


118-119: Adhere to the coding guideline for negation checks.
Replace !queryIsCaseSensitive with false == queryIsCaseSensitive for consistency.

-handleQuerySubmit({queryIsCaseSensitive: !queryIsCaseSensitive});
-setQueryIsCaseSensitive(!queryIsCaseSensitive);
+handleQuerySubmit({queryIsCaseSensitive: false == queryIsCaseSensitive});
+setQueryIsCaseSensitive(false == queryIsCaseSensitive);

123-124: Maintain consistency for the regex negation as well.
Similarly, use false == queryIsRegex instead of !queryIsRegex.

-handleQuerySubmit({queryIsRegex: !queryIsRegex});
-setQueryIsRegex(!queryIsRegex);
+handleQuerySubmit({queryIsRegex: false == queryIsRegex});
+setQueryIsRegex(false == queryIsRegex);
📜 Review details

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

📥 Commits

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

📒 Files selected for processing (7)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (8 hunks)
  • src/contexts/StateContextProvider.tsx (4 hunks)
  • src/contexts/UrlContextProvider.tsx (4 hunks)
  • src/services/LogFileManager/index.ts (2 hunks)
  • src/typings/query.ts (1 hunks)
  • src/typings/url.ts (1 hunks)
  • src/typings/worker.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • src/contexts/StateContextProvider.tsx
  • src/typings/url.ts
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}`: - Prefer `false == ...

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

  • src/typings/worker.ts
  • src/typings/query.ts
  • src/services/LogFileManager/index.ts
  • src/contexts/UrlContextProvider.tsx
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx
🪛 GitHub Check: lint-check
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx

[failure] 81-81:
This line has a length of 109. Maximum allowed is 100


[failure] 86-86:
React Hook useEffect has missing dependencies: 'startQuery', 'urlQueryIsCaseSensitive', and 'urlQueryIsRegex'. Either include them or remove the dependency array

🪛 GitHub Actions: lint
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx

[warning] 81-81: This line has a length of 109. Maximum allowed is 100 @stylistic/max-len

🔇 Additional comments (22)
src/typings/worker.ts (1)

115-116: LGTM! Parameter renaming improves code clarity.

The renaming of parameters to queryIsCaseSensitive and queryIsRegex enhances code readability by explicitly indicating these parameters are related to query operations.

src/typings/query.ts (1)

3-4: LGTM! Consistent parameter naming improves maintainability.

Renaming these properties to queryIsCaseSensitive and queryIsRegex aligns with the changes in worker.ts, ensuring consistency across the codebase.

src/services/LogFileManager/index.ts (3)

295-296: LGTM! JSDoc updates match parameter renaming.

The JSDoc parameter descriptions have been correctly updated to reflect the renamed parameters.


298-298: Function signature properly updated to match type changes.

The method signature has been updated to use the new parameter names, maintaining consistency with the type changes.


312-317: LGTM! Variable references updated to match new parameter names.

The internal code has been appropriately updated to reference the new parameter names.

src/contexts/UrlContextProvider.tsx (4)

34-36: LGTM! New default hash parameters added for query sharing.

The addition of these parameters to the default object enables the sharing feature for search parameters.


107-107: LGTM! Condition properly handles false boolean values.

The condition now correctly removes parameters when their value is false, which aligns with the expected behavior for boolean toggle parameters.


187-190: Boolean type conversion is required for URL parameters.

The UrlSearchParams interface may define boolean types, but URLSearchParams stores them as strings. Type conversion is necessary for type safety.


221-235: LGTM! Proper handling of query parameters from URL hash.

The implementation correctly retrieves and type-converts the query parameters from the URL hash. The string to boolean conversion is properly handled using string comparison.

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

3-3: No concerns regarding the import of useEffect.
It is properly added and necessary for the upcoming effect logic.


15-15: The new icon import is a beneficial addition.
Importing ShareIcon is straightforward and aligns with the sharing feature.


20-25: Appropriate imports from UrlContextProvider.
They are correctly declared and will be useful for URL manipulation and sharing.


30-33: UI_ELEMENT and UI_STATE usage is correct.
These are likely being used in the effect and logic with no apparent issues.


56-60: Destructuring queryString, queryIsCaseSensitive, queryIsRegex is implemented correctly.
No concerns here; it cleanly retrieves values from the UrlContext.


63-64: State initialization for case sensitivity and regex flags is clear.
Setting both to false by default is logical.


94-101: handleShareButtonClick function is straightforward.
Copying the permalink to the clipboard appears well-implemented for sharing the link.


105-106: handleQuerySubmit integration looks correct.
Referencing the new case-sensitivity and regex state flags aligns with the updated logic.


130-130: No concerns with the updated panel container line.
The panel’s setup remains intact.


134-151: New share button in the panel UI is well integrated.
It complements the existing collapse/expand button, enhancing user experience for link sharing.


161-161: Binding the textarea’s value to queryString is correct.
Ensures the component reflects the current search input accurately.


170-171: isChecked={queryIsCaseSensitive} logic is fine.
No issues flagged by the new approach for toggling case-sensitivity.


182-183: isChecked={queryIsRegex} logic is also good.
The toggle correctly binds to the updated state for regex mode.

@Henry8192 Henry8192 requested a review from a team as a code owner February 27, 2025 22:15
@Henry8192 Henry8192 requested a review from junhaoliao February 27, 2025 22:16
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: 2

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

78-103: Follow coding guidelines for conditional checks.

According to the coding guidelines, false == <expression> should be preferred over !<expression>.

-            if (null !== urlQueryString) {
+            if (null !== urlQueryString) {

While this particular line already follows the guidelines, ensure all conditional checks throughout the component maintain this style.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c6b97a9 and 7dd50b9.

📒 Files selected for processing (1)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (8 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}`: - Prefer `false == ...

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

  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx
🔇 Additional comments (5)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (5)

108-115: Good implementation of sharing functionality.

The handleShareButtonClick method correctly captures the current search state and uses copyPermalinkToClipboard to share it.


70-76: Good use of refs to track URL context values.

Using refs to track the URL context values helps prevent unnecessary re-renders while still keeping the component responsive to URL changes.


91-96: Good formatting for line length compliance.

The multi-line formatting for the hash parameters object effectively prevents line length issues that were flagged in previous reviews.


148-165: Well-structured UI addition for share button.

The share button is implemented consistently with the existing UI patterns, using the same component structure as the collapse/expand button.


99-103: Properly handled useEffect dependencies.

The useEffect now correctly includes startQuery in the dependency array, addressing the issue raised in the previous review.

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

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

103-107: Consider adding URL query parameters to the dependency array.

The useEffect dependency array is missing urlQueryIsCaseSensitive and urlQueryIsRegex. Even though you're using refs to track these values, changes to these URL parameters should trigger the effect to ensure the component properly reacts to URL changes.

 }, [
     startQuery,
     uiState,
     urlQueryString,
+    urlQueryIsCaseSensitive,
+    urlQueryIsRegex,
 ]);
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7dd50b9 and 691a911.

📒 Files selected for processing (2)
  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (8 hunks)
  • src/services/LogFileManager/index.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/services/LogFileManager/index.ts
🧰 Additional context used
📓 Path-based instructions (1)
`**/*.{cpp,hpp,java,js,jsx,tpp,ts,tsx}`: - Prefer `false == ...

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

  • src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx
🔇 Additional comments (6)
src/components/CentralContainer/Sidebar/SidebarTabs/SearchTabPanel/index.tsx (6)

112-119: Good implementation of share functionality.

The handleShareButtonClick function correctly implements the link sharing feature by calling copyPermalinkToClipboard with the current search parameters.


136-137: Toggle implementation using negation operator.

According to the coding guidelines, false == <expression> should be preferred over !<expression>. However, as discussed in previous comments, using ! here makes the toggling action more intuitive to understand.


152-169: Well-structured UI for sharing functionality.

The addition of the share button in the title area is cleanly implemented with proper tooltips and icon. Good job maintaining consistent UI patterns with the existing collapse/expand button.


95-101: Consider the intent of resetting URL parameters.

This code updates the window URL hash parameters to their default values right after starting a query with custom parameters. Is the intention to reset the URL after starting the query? If not, this might counteract the sharing functionality you're implementing.

Please confirm if this is intentional behavior - typically when implementing shareable URLs, you would want the URL to reflect the current search parameters rather than resetting them to defaults.


84-93: Good state initialization from URL parameters.

The implementation correctly initializes the search component's state from URL parameters and starts the query with those parameters when the UI is ready.


67-76: Effective use of refs for tracking URL context values.

Using refs to track the URL context values between renders is a good approach to maintain values while avoiding unnecessary re-renders.

@@ -38,21 +51,77 @@ import "./index.css";
*
* @return
*/
// eslint-disable-next-line max-lines-per-function
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
// eslint-disable-next-line max-lines-per-function

We should avoid disabling linting rules whenever possible. Please see if the refactoring PR at #196 properly addresses this violation.

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