Rename Tidb to LabelDb

[kimhanbeom]

Close: #121

[gemini-code-assist]

Summary of Changes

Hello @kimhanbeom, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request undertakes a significant refactoring effort to standardize naming conventions by renaming 'Tidb' (Threat Intelligence Database) to 'LabelDb' (Label Database) and updating all associated types, methods, and request codes. This change aims to provide clearer and more generic terminology, improving the maintainability and understanding of the codebase, albeit introducing a breaking change as noted in the changelog.

Highlights

• Core Renaming: The primary change involves renaming all references of Tidb to LabelDb throughout the codebase, including related types and methods.
• Type Renames: The TiKind enum has been renamed to LabelDbKind, and the TiRule struct has been renamed to LabelDbRule to align with the new LabelDb terminology.
• API and Handler Updates: Client-side API methods (e.g., get_tidb_patterns to get_labeldb_patterns), server-side request codes (RequestCode::GetTidbPatterns to RequestCode::GetLabelDbPatterns), and server handler traits have been updated to reflect the new naming conventions.
• Changelog Entry: A new entry has been added to CHANGELOG.md for the unreleased version, explicitly stating these renames as a breaking change.
• Typo Correction: A minor typo in CHANGELOG.md was corrected, changing respond_with_tidb_patters to respond_with_tidb_patterns.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request performs a comprehensive renaming of Tidb and related types to LabelDb across the codebase. The changes are consistent and well-executed, covering API functions, types, documentation, and tests. I've found one minor formatting issue in the CHANGELOG.md file. Otherwise, the changes look good.

[gemini-code-assist]

There's a minor formatting issue here. For consistency with other entries in this file, please add a space before (Breaking Change) and a period at the end of the line.

Suggested change

	- Renamed `Tidb` references to `LabelDb` (including request codes/handler-client
	methods) and `TiKind`/`TiRule` to `LabelDbKind`/`LabelDbRule`(Breaking Change)
	- Renamed `Tidb` references to `LabelDb` (including request codes/handler-client
	methods) and `TiKind`/`TiRule` to `LabelDbKind`/`LabelDbRule` (Breaking Change).

[codecov]

Codecov Report

❌ Patch coverage is 75.00000% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.99%. Comparing base (2598d5b) to head (fe44b20).

Files with missing lines	Patch %	Lines
src/server.rs	0.00%	2 Missing ⚠️
src/server/handler.rs	50.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #122   +/-   ##
=======================================
  Coverage   86.99%   86.99%           
=======================================
  Files          11       11           
  Lines        2330     2330           
=======================================
  Hits         2027     2027           
  Misses        303      303           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.