chore(server): add logs to item import cmd

[yk-eukarya]

Summary by CodeRabbit

• Improvements

  • Enhanced logging during item import process
  • Improved visibility into import workflow
  • Updated error messaging for import operations

• Bug Fixes

  • Refined item import logging to provide progress feedback

[coderabbitai]

Walkthrough

The pull request introduces enhanced logging mechanisms for the item import process across two key files: server/cmd/reearth-cms/main.go and server/internal/usecase/interactor/item.go. The changes focus on providing more detailed progress tracking during item imports, with logging statements added to report the number of items processed at regular intervals (every 1,000 items) and at the end of the import operation. The modifications aim to improve visibility and debugging capabilities for the import workflow.

Changes

File	Change Summary
server/cmd/reearth-cms/main.go	- Added log statement at the start of item import process - Modified itemsFromJson function to include index-based logging every 1000 items - Added final log statement reporting total items prepared
server/internal/usecase/interactor/item.go	- Enhanced logging in Import method to track item creation progress - Updated error messaging in Import2 method - Added index-based logging for item processing

Possibly related PRs

• fix(server): importing items when it contains id #1284: Modifies Import method in item.go, related to import logging
• chore(server): move export csv items and GeoJSON ability to Item Usecase Layer #1347: Changes to Item struct affecting import functionality
• feat(server): command line for import items #1371: Introduces CLI for item importing

Suggested labels

server

Poem

🐰 Importing items, hop by hop,
Logs dancing, never want to stop!
Thousand items, a rabbit's delight,
Tracking progress with all my might
Import magic, clear and bright! 🚀

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

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. (Beta)
• @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.

[netlify]

✅ Deploy Preview for reearth-cms canceled.

Name	Link
🔨 Latest commit	2118300
🔍 Latest deploy log	https://app.netlify.com/sites/reearth-cms/deploys/679a34b6677b82000833b324

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (4)

server/cmd/reearth-cms/main.go (2)

256-258: Enhance progress message clarity.

The progress message could be more descriptive to better indicate the stage of the process.

-      log.Infof("%d items prepared...", i)
+      log.Infof("Processing items from JSON: %d items prepared...", i)

---

260-261: Consolidate completion messages.

The completion messages are redundant. Consider combining them into a single, more informative message.

-    log.Infof("%d items prepared.", len(items))
-    log.Infof("items preparation done.")
+    log.Infof("JSON processing complete: %d items prepared successfully.", len(items))

server/internal/usecase/interactor/item.go (2)

591-593: Enhance progress message clarity.

The progress message could be more descriptive to better indicate the stage of the process.

-      log.Infof(" %d items created...", j)
+      log.Infof("Import progress: %d items created...", j)

---

595-595: Enhance completion messages with more context.

The completion messages could be more informative by including additional context.

-    log.Infof(" %d items created.", len(param.Items))
+    log.Infof("Import complete: %d items created successfully.", len(param.Items))

-    log.Infof(" %d threads saved.", len(threadsToSave))
+    log.Infof("Thread creation complete: %d threads saved successfully.", len(threadsToSave))

-    log.Infof(" %d items saved.", len(itemsToSave))
+    log.Infof("Item persistence complete: %d items saved successfully.", len(itemsToSave))

Also applies to: 600-600, 605-605

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f6abbfc and 2118300.

📒 Files selected for processing (2)

• server/cmd/reearth-cms/main.go (3 hunks)
• server/internal/usecase/interactor/item.go (3 hunks)

🔇 Additional comments (3)

server/cmd/reearth-cms/main.go (1)

121-122: LGTM!

Clear initial log message indicating the start of the import process.

server/internal/usecase/interactor/item.go (2)

448-448: LGTM!

Clear log message for schema updates with field count.

---

686-686: LGTM!

Good improvement to the error message by wrapping it with more context.