feat: table - export searchTerm

[superstes]

Closes #1560

📑 Description

Exports the searchTerm of the Table component so users can set its initial value.

Status

• Not Completed
• Completed

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• I have checked the page with https://validator.unl.edu/
• All the tests have passed
• My pull request is based on the latest commit (not the npm version).

Summary by CodeRabbit

• New Features
  • Introduced an optional search input for the table component, allowing users to filter results more effectively. The search value now defaults to an empty string for consistent behavior.
• Documentation
  • Updated component documentation to include details on the new search feature, ensuring users understand its usage and behavior.

[vercel]

@superstes is attempting to deploy a commit to the Themesberg Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The pull request introduces an optional searchTerm property to the Table component. In Table.svelte, the property is added to the $$Props interface and exported as a reactive variable with a default value of an empty string. The reactive statement updating the searchTermStore is adjusted to default to an empty string when falsy. In addition, the corresponding JSON configuration file (Table.json) is updated to document this new property.

Changes

Files	Change Summary
src/lib/table/Table.svelte src/routes/.../Table.json	Added new optional property searchTerm of type string with default value ''. In Table.svelte, updated the interface, reactive variable export, and store update; in Table.json, added proper documentation in the props array.

Assessment against linked issues

Objective	Addressed	Explanation
Export and document searchTerm property [#1560]	✅

Possibly related PRs

• feat: implement sorting and searching in Table component #1425: Introduces similar changes to the Table component by enhancing the handling of the searchTerm property, aligning with the modifications in this pull request.

Poem

I’m a little bunny, hopping along the code lane,
With a new search term, my logic’s now spruced and plain.
Every empty string is a field of carrot delight,
No undefined missteps to give my code a bite.
Hoppin’ with joy in every line that’s newly made—cheers to upgrades!

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

src/lib/table/Table.svelte

Oops! Something went wrong! :(

ESLint: 9.22.0

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@eslint/js' imported from /eslint.config.js
at packageResolve (node:internal/modules/esm/resolve:839:9)
at moduleResolve (node:internal/modules/esm/resolve:908:18)
at defaultResolve (node:internal/modules/esm/resolve:1038:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:557:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:525:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:246:38)
at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/lib/table/Table.svelte (1)

72-72: Consider using nullish coalescing for the fallback

The ternary operator works, but the nullish coalescing operator would be more idiomatic for this case.

-  $: searchTermStore.set(searchTerm ? searchTerm : '');
+  $: searchTermStore.set(searchTerm ?? '');

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2e81484 and 80e2e37.

📒 Files selected for processing (2)

• src/lib/table/Table.svelte (4 hunks)
• src/routes/component-data/Table.json (1 hunks)

🔇 Additional comments (4)

src/routes/component-data/Table.json (1)

22-23: LGTM: searchTerm property correctly documented

The addition of the searchTerm property to the Table component's JSON definition is correctly implemented with the appropriate type and default value.

src/lib/table/Table.svelte (3)

26-26: LGTM: Property correctly added to interface

The searchTerm property is correctly added to the $$Props interface with the appropriate type.

---

46-46: LGTM: Property correctly exported

The searchTerm property is properly exported with the correct type reference and default value.

---

124-124: LGTM: Documentation correctly updated

The component documentation is properly updated to include the new property.