HTMLタグを削除する関数とテキスト用のハッシュ生成関数を追加し、関連するファイルを整理しました。また、コンポーネントのインポートパスを更新しました。

[ttizze]

Summary by CodeRabbit

• Refactor

  • Streamlined internal module references and directory organization across the project, including updates to import paths for various components and functions.

• Chore

  • Updated configuration files and test setups to align with the new structure.

These changes enhance code maintainability and consistency without affecting any user-facing functionality.

[coderabbitai]

Walkthrough

This pull request refactors numerous import paths throughout the codebase. Files across various areas such as components, database queries/mutations, libraries, constants, and scripts now reference new directories with an underscore prefix (e.g., from /components/ to /_components/, from /db/ to /_db/, from /lib/ to /_lib/, and from /constants/ to /_constants/). There are no functional or logical changes; the updates strictly reflect a restructuring of the file organization.

Changes

Files	Change Summary
.../(common-layout)/about/page.tsx, .../auth/login/login.tsx, .../layout.tsx, .../(common-layout)/page.tsx, .../_components/hero-section/index.tsx, etc.	Updated UI component imports from /components/ to /_components/ (e.g., HeroSection, GoogleForm, Header, Footer).
.../search/_db/queries.server.ts, .../user/[handle]/_components/page-list.server.tsx, .../user/[handle]/edit/*.ts, .../api/pages/db/queries.server.ts, etc.	Updated database query and mutation imports from /db/ to /_db/ across multiple modules and test files.
.../api/og/route.tsx, .../sitemap.ts, .../features/translate/lib/translate.server.ts, etc.	Refactored utility library and constant imports from /lib/ to /_lib/ and from /constants/ to /_constants/.
next/tsconfig.json, next/scripts/processMarkdownContent.ts, next/scripts/syncDB.ts, next/scripts/syncGIthub.ts	Modified file inclusion paths and script imports to align with the new directory structure.

Possibly related PRs

• 動的インポートを使用してコンポーネントのローディング状態を追加し、いくつかのコンポーネントを最適化しました #600: The changes involve updating import paths for components and modules to reflect a new directory structure, similar to this PR's modifications.
• ページ管理機能を動的インポートに変更し、クライアントコンポーネントを追加しました。また、ページデータの取得ロジックを整理しました。 #644: This PR also includes modifications to import paths for components and functions, indicating a similar restructuring of the directory organization.
• BASE_URL定数を使用してサイトマップのURL生成ロジックを更新し、ページ情報を取得するAPIを追加 #665: Related to this PR as it involves modifications to import paths for database queries, specifically changing from a db directory to a _db directory.

Poem

I'm a little rabbit, hopping with glee,
Restructuring paths so the code stays free.
From old "components" to a new "_components" way,
The files now sing in a bright, fresh display.
Tiny tweaks, smooth as a hop,
Our code garden's neat on every stop!
🐇🌟

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f520568 and 61fd216.

📒 Files selected for processing (1)

• next/src/app/[locale]/(edit-layout)/user/[handle]/page/[slug]/edit/_components/editor/use-file-upload.ts (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• next/src/app/[locale]/(edit-layout)/user/[handle]/page/[slug]/edit/_components/editor/use-file-upload.ts

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Analyze (javascript-typescript)

---

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

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