Skip to content

feat: Implement Shift-click range selection for keywords#293

Open
abhranil26 wants to merge 2 commits into
towfiqi:mainfrom
abhranil26:feature/shift-click-keyword-selection
Open

feat: Implement Shift-click range selection for keywords#293
abhranil26 wants to merge 2 commits into
towfiqi:mainfrom
abhranil26:feature/shift-click-keyword-selection

Conversation

@abhranil26

Copy link
Copy Markdown

This commit introduces the ability to select a range of keywords by holding down the Shift key while clicking.

Key changes:

  • Modified components/keywords/KeywordsTable.tsx:
    • The selectKeyword function now accepts an optional mouse event.
    • If the Shift key is pressed during a click, it identifies the last selected keyword and the currently clicked keyword.
    • All keywords between these two (inclusive) are then selected. Existing selections outside this range are preserved.
  • Updated components/keywords/Keyword.tsx:
    • The onClick handler for the keyword selection checkbox now passes the mouse event to the selectKeyword function.
    • Added data-testid attributes to keyword rows and checkboxes to facilitate testing.
  • Added unit tests in __tests__/components/KeywordsTable.test.tsx:
    • Created new test suite for KeywordsTable.
    • Implemented comprehensive tests covering various Shift-click scenarios, including forward, reverse, and disjointed selections, as well as interactions with normal clicks.

This enhancement improves the usability of keyword selection, allowing you to more efficiently manage large lists of keywords.

This commit introduces the ability to select a range of keywords by holding down the Shift key while clicking.

Key changes:

- Modified `components/keywords/KeywordsTable.tsx`:
    - The `selectKeyword` function now accepts an optional mouse event.
    - If the Shift key is pressed during a click, it identifies the last selected keyword and the currently clicked keyword.
    - All keywords between these two (inclusive) are then selected. Existing selections outside this range are preserved.
- Updated `components/keywords/Keyword.tsx`:
    - The `onClick` handler for the keyword selection checkbox now passes the mouse event to the `selectKeyword` function.
    - Added `data-testid` attributes to keyword rows and checkboxes to facilitate testing.
- Added unit tests in `__tests__/components/KeywordsTable.test.tsx`:
    - Created new test suite for `KeywordsTable`.
    - Implemented comprehensive tests covering various Shift-click scenarios, including forward, reverse, and disjointed selections, as well as interactions with normal clicks.

This enhancement improves the usability of keyword selection, allowing you to more efficiently manage large lists of keywords.
This commit corrects various linting errors and import path issues identified in the previous commit.

Corrections in `__tests__/components/KeywordsTable.test.tsx`:
- Resolved critical path errors for `KeywordType`, `SettingsType`, and `DomainType` by updating import paths to `../../types`.
- Added `displayName` to all mocked functional components (Icon, Keyword, KeywordDetails, KeywordFilter, Modal, Toaster, FixedSizeList) to prevent 'missing display name' warnings.
- Fixed code style issues:
    - Reformatted long lines in `mockKeywords` data to improve readability and adhere to character limits.
    - Added missing trailing commas.
    - Removed excessive blank lines.
    - Corrected spacing in the `react-hot-toast` mock.
    - Ensured object properties in `mockDomain` and `mockSettings` are on new lines for better formatting.

Correction in `components/keywords/KeywordsTable.tsx`:
- Removed unnecessary blank line padding within the `selectKeyword` function to resolve a 'Block must not be padded by blank lines' error.

These changes ensure the codebase adheres to linting standards and resolves import errors, improving code quality and maintainability.
@gigerIT

gigerIT commented Mar 25, 2026

Copy link
Copy Markdown

We had the same idea and other issues and ended up forking SerpBear to address them:
https://github.com/gigerIT/serpbear

Since then, we’ve fixed several critical bugs and also resolved high-severity security issues. We’re continuously improving the project and moving quickly, as we rely on it for our own client work. Keeping the fork stable, up to date, and production-ready is a priority for us.

We’ve also introduced CI (testing + automated releases) to ensure improvements are shipped consistently and reliably.

Multi-user support, outdated documentation, and improved local/city-level tracking are all on our roadmap and being worked on step by step.

If you want to try it out, you can switch to our fork as a drop-in replacement using our Docker image:
gigeritch/serpbear:latest

Sharing this in case it’s useful to others.

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