Skip to content

chore: rename#1

Merged
hmbanan666 merged 3 commits into
mainfrom
rename
Jul 17, 2025
Merged

chore: rename#1
hmbanan666 merged 3 commits into
mainfrom
rename

Conversation

@hmbanan666
Copy link
Copy Markdown
Collaborator

@hmbanan666 hmbanan666 commented Jul 17, 2025

Summary by CodeRabbit

  • Chores

    • Updated all package names and dependencies from @sushi-atrium to @roll-stack across the project.
    • Adjusted configuration files and workflow inputs to reflect the new naming convention.
    • Updated VSCode settings to include new SonarLint project connection details.
  • Refactor

    • Improved image metadata validation by extracting validation logic into a dedicated helper function.
  • Style

    • No user-facing changes to application features or functionality. All updates are related to naming and configuration.

@hmbanan666 hmbanan666 self-assigned this Jul 17, 2025
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jul 17, 2025

Walkthrough

This change updates all package references, import paths, and configuration entries from the @sushi-atrium namespace to the new @roll-stack namespace across the codebase. The update affects package metadata, dependencies, import statements, workflow regex patterns, and related configuration files. Additionally, a helper function for image metadata validation was introduced. No other functional or logic changes were made.

Changes

Files/Paths Change Summary
.github/workflows/docker-release.yml Updated workflow input descriptions and regex patterns from @sushi-atrium to @roll-stack.
.vscode/settings.json Added SonarLint connected mode settings for sushi-love_roll-stack.
apps/geo-vault/package.json, apps/web-app/package.json, apps/web-parser/package.json Changed package names and dependencies from @sushi-atrium/* to @roll-stack/*.
apps/geo-vault/server/..., apps/web-app/server/... (API, plugins, tasks, utils) Updated all import paths from @sushi-atrium/geo-database or @sushi-atrium/database to @roll-stack/....
apps/web-app/app/components/..., apps/web-app/app/pages/..., apps/web-app/stores/..., apps/web-app/types/index.ts Changed all type and module imports from @sushi-atrium/database to @roll-stack/database.
apps/web-app/nuxt.config.ts Changed UI extension import from @sushi-atrium/ui to @roll-stack/ui.
apps/web-app/server/api/post/id/[postId]/image.post.ts Extracted image metadata validation logic into new helper function validateMetadata.
apps/web-app/server/utils/tests/unit/avatar.spec.ts Changed test assertion from toMatchInlineSnapshot to toEqual for getPossibleSkinColors.

Poem

🐇
A hop from sushi to roll,
Our code now plays a brand new role.
Imports aligned, the names all stack,
No logic changed, just a namespace track.
With every change, the system’s whole—
A rolling rabbit, on a roll!
🍣➡️🥢


📜 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 96a551e and b90f147.

📒 Files selected for processing (1)
  • apps/web-app/server/api/post/id/[postId]/image.post.ts (3 hunks)
✅ Files skipped from review due to trivial changes (1)
  • apps/web-app/server/api/post/id/[postId]/image.post.ts
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🔭 Outside diff range comments (4)
apps/web-app/app/pages/product/[productId]/usage.vue (1)

56-58: Broken CSS selector-parentheses – UI will not compile
Extra ) inside the td selector causes an invalid Tailwind/CSS class.

-        td: 'border-b border-default [&:has([data-media=true]))]:px-0 [&:has([data-media=true]))]:max-w-10 [&:has([data-action=true]))]:pr-0',
+        td: 'border-b border-default [&:has([data-media=true])]:px-0 [&:has([data-media=true])]:max-w-10 [&:has([data-action=true])]:pr-0',
apps/web-app/server/api/chat/index.post.ts (1)

21-23: Guard logic is too strict – blocks valid requests
The intention is to reject when the member list is empty or the current user is missing.
Current condition only fires when both are true.

-    if (data.usersId.length === 0 && !data.usersId.includes(session.user.id)) {
+    if (data.usersId.length === 0 || !data.usersId.includes(session.user.id)) {
apps/web-app/server/api/task/list/id/[listId].patch.ts (1)

41-44: instanceof type.errors is unlikely to work.

type.errors isn’t a constructor but a static property; instanceof will therefore always be false.
Consider checking with Array.isArray(data) or whatever arktype actually returns for validation errors.

apps/web-app/server/api/post/id/[postId]/comment.post.ts (1)

23-26: Same validation issue as in task list handler.

instanceof type.errors likely never matches. Use the proper guard recommended by arktype.

-if (data instanceof type.errors) {
-  throw data
-}
+if (type.errors.is(data)) { // or whatever helper arktype exposes
+  throw data
+}
♻️ Duplicate comments (17)
apps/web-app/server/api/print/id/[printId].patch.ts (1)

1-1: Same namespace rename as above – the caution about dependency/paths applies here too.

apps/web-app/server/api/print/index.post.ts (1)

1-1: Same namespace rename as above – please ensure the new package is correctly referenced.

apps/web-app/server/api/task/index.post.ts (1)

1-1: Same namespace rename as above – verify dependency & TS path mappings.

apps/web-app/server/api/partner/list.get.ts (1)

1-1: Same namespace rename as above – confirm package resolution across all workspaces.

apps/web-app/server/api/user/id/[userId]/online.post.ts (1)

1-1: Namespace-swap comment already covered in previous review

Same one-line import change; see earlier note for verification script and dependency check.

apps/web-app/server/api/task/list/index.post.ts (1)

1-1: Namespace-swap comment already covered in previous review

Same one-line import change; see earlier note for verification script and dependency check.

apps/web-app/server/api/chat/id/[chatId]/message/index.post.ts (1)

1-1: Namespace-swap comment already covered in previous review

Same one-line import change; see earlier note for verification script and dependency check.

apps/web-app/server/api/user/list/staff.get.ts (1)

1-1: Namespace-swap comment already covered in previous review

Same one-line import change; see earlier note for verification script and dependency check.

apps/web-app/app/pages/kitchen/index.vue (1)

142-142: Same verification comment applies

Import source switched to @roll-stack/database; ensure the dependency exists and no old namespace remains elsewhere.

apps/web-app/server/api/post/id/[postId]/like.post.ts (1)

1-1: Same namespace swap here – covered by previous comment

apps/web-app/stores/notification.ts (1)

1-1: Namespace swap acknowledged

apps/web-app/server/api/chat/id/[chatId]/index.get.ts (1)

1-1: Namespace swap acknowledged

apps/web-app/server/api/chat/id/[chatId]/message/list.get.ts (1)

1-1: Namespace swap acknowledged

apps/web-app/server/api/product/variant/id/[variantId]/index.delete.ts (1)

1-1: Same namespace swap applied here

Nothing further—see the verification note on the first file.

apps/web-app/server/api/task/list/completed.get.ts (1)

1-1: Namespace rename acknowledged

Change mirrors earlier files; prior remarks still apply.

apps/web-app/server/api/task/list/index.get.ts (1)

1-1: Consistent import update

No additional issues spotted beyond the original verification request.

apps/web-app/server/api/auth/me.get.ts (1)

1-1: Import path renamed correctly

Everything else remains untouched; earlier verification script covers this case too.

🧹 Nitpick comments (7)
.vscode/settings.json (1)

68-72: Consider renaming the Sonar connection id for clarity
connectionId is still "sushi-love" while the project key is "sushi-love_roll-stack".
If the backend project was also re-scoped, using a neutral id such as "roll-stack" avoids confusion.

apps/web-app/stores/user.ts (2)

18-20: Avoid “undefined undefined” in fullName.
When either name or surname is still undefined you end up returning the string "undefined" which is what gets rendered to the UI.

-  const fullName = computed(() => {
-    return `${name.value} ${surname.value}`
-  })
+  const fullName = computed(() => {
+    return [name.value, surname.value].filter(Boolean).join(' ')
+  })

25-32: DRY up the repeated $fetch option objects.

The same { lazy, server, cache, getCachedData } set appears in three places.
Extracting a small helper (or at least a constant) will cut noise and avoid accidental drift.

Example:

const noCacheOpts = { lazy: true, server: true, cache: 'no-cache', getCachedData: undefined }

// …
await $fetch('/api/auth/me', noCacheOpts)

Also applies to: 60-67, 88-94

apps/web-app/types/index.ts (1)

1-1: Types import updated – check TS path aliases

Only the import path was changed. If tsconfig.json/paths or Nuxt’s alias config still mention @sushi-atrium/database, type resolution may fail in IDEs even if the runtime package is correct. Ensure those configs were updated in the same PR.

apps/web-app/app/components/form/CreatePost.vue (1)

95-95: Type import migrated – watch for TS path config

Post now comes from @roll-stack/database. Ensure your tsconfig.paths (or Nuxt alias) is already updated; otherwise TypeScript may still resolve the old scope in editor tooling.

apps/web-app/server/api/task/id/[taskId]/complete.post.ts (1)

1-2: Combine duplicate imports from the same module.

You now have two separate import statements from @roll-stack/database. Consolidating them reduces noise and ensures tree-shaking behaves consistently.

-import type { Task, User } from '@roll-stack/database'
-import { repository } from '@roll-stack/database'
+import type { Task, User } from '@roll-stack/database'
+import { repository } from '@roll-stack/database'

(No other lines need to change.)

.github/workflows/docker-release.yml (1)

10-10: Tighten the regex to avoid accidental matches.

Consider anchoring and properly escaping dots so the pattern only matches fully-qualified tags:

-        description: 'ex: @roll-stack/web-app-v1.0.0'
+        description: 'ex: @roll-stack/web-app-v1.0.0'

-          regex: '@roll-stack\/([a-z-]+)-(v[0-9]+.[0-9]+.[0-9]+)'
+          # ^ start, $ end, escaped dots
+          regex: '^@roll-stack\\/([a-z-]+)-(v[0-9]+\\.[0-9]+\\.[0-9]+)$'

Without the anchors the action may pick up substrings inside longer refs and produce unexpected outputs.

Also applies to: 31-31

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7202678 and aa896fe.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (107)
  • .github/workflows/docker-release.yml (2 hunks)
  • .vscode/settings.json (1 hunks)
  • apps/geo-vault/package.json (2 hunks)
  • apps/geo-vault/server/api/address/index.post.ts (1 hunks)
  • apps/geo-vault/server/api/geo/house-parents.get.ts (1 hunks)
  • apps/geo-vault/server/api/geo/houses.get.ts (1 hunks)
  • apps/geo-vault/server/api/geo/object-parents.get.ts (1 hunks)
  • apps/geo-vault/server/api/geo/objects.get.ts (1 hunks)
  • apps/geo-vault/server/plugins/01.database.ts (1 hunks)
  • apps/web-app/app/components/CheckoutItem.vue (1 hunks)
  • apps/web-app/app/components/ClientReviewCard.vue (1 hunks)
  • apps/web-app/app/components/FeedbackPointsBlock.vue (1 hunks)
  • apps/web-app/app/components/KitchenCard.vue (1 hunks)
  • apps/web-app/app/components/PartnerCard.vue (1 hunks)
  • apps/web-app/app/components/PostImage.vue (1 hunks)
  • apps/web-app/app/components/ProductImage.vue (1 hunks)
  • apps/web-app/app/components/ProductTagsBlock.vue (1 hunks)
  • apps/web-app/app/components/StaffCard.vue (1 hunks)
  • apps/web-app/app/components/TaskCard.vue (1 hunks)
  • apps/web-app/app/components/TaskPopover.vue (1 hunks)
  • apps/web-app/app/components/UserPopover.vue (1 hunks)
  • apps/web-app/app/components/form/CreatePost.vue (1 hunks)
  • apps/web-app/app/components/form/UpdatePost.vue (1 hunks)
  • apps/web-app/app/pages/head/task/index.vue (1 hunks)
  • apps/web-app/app/pages/kitchen/index.vue (1 hunks)
  • apps/web-app/app/pages/post/index.vue (1 hunks)
  • apps/web-app/app/pages/print/index.vue (1 hunks)
  • apps/web-app/app/pages/product/[productId]/usage.vue (1 hunks)
  • apps/web-app/app/pages/product/index.vue (1 hunks)
  • apps/web-app/nuxt.config.ts (1 hunks)
  • apps/web-app/package.json (2 hunks)
  • apps/web-app/server/api/auth/me.get.ts (1 hunks)
  • apps/web-app/server/api/auth/sign-in.post.ts (1 hunks)
  • apps/web-app/server/api/chat/id/[chatId]/index.get.ts (1 hunks)
  • apps/web-app/server/api/chat/id/[chatId]/message/index.post.ts (1 hunks)
  • apps/web-app/server/api/chat/id/[chatId]/message/list.get.ts (1 hunks)
  • apps/web-app/server/api/chat/index.post.ts (1 hunks)
  • apps/web-app/server/api/chat/my/index.get.ts (1 hunks)
  • apps/web-app/server/api/checkout/list.get.ts (1 hunks)
  • apps/web-app/server/api/client/review/list.get.ts (1 hunks)
  • apps/web-app/server/api/health/index.get.ts (1 hunks)
  • apps/web-app/server/api/kitchen/list.get.ts (1 hunks)
  • apps/web-app/server/api/menu/category/id/[categoryId]/index.delete.ts (1 hunks)
  • apps/web-app/server/api/menu/category/id/[categoryId]/index.patch.ts (1 hunks)
  • apps/web-app/server/api/menu/category/id/[categoryId]/product.delete.ts (1 hunks)
  • apps/web-app/server/api/menu/category/id/[categoryId]/product.post.ts (1 hunks)
  • apps/web-app/server/api/menu/category/index.post.ts (1 hunks)
  • apps/web-app/server/api/menu/list.get.ts (1 hunks)
  • apps/web-app/server/api/notification/my.get.ts (1 hunks)
  • apps/web-app/server/api/partner/list.get.ts (1 hunks)
  • apps/web-app/server/api/payment/method/list.get.ts (1 hunks)
  • apps/web-app/server/api/post/comment/id/[commentId]/index.delete.ts (1 hunks)
  • apps/web-app/server/api/post/id/[postId]/comment.post.ts (1 hunks)
  • apps/web-app/server/api/post/id/[postId]/image.post.ts (1 hunks)
  • apps/web-app/server/api/post/id/[postId]/index.delete.ts (1 hunks)
  • apps/web-app/server/api/post/id/[postId]/index.patch.ts (1 hunks)
  • apps/web-app/server/api/post/id/[postId]/like.delete.ts (1 hunks)
  • apps/web-app/server/api/post/id/[postId]/like.post.ts (1 hunks)
  • apps/web-app/server/api/post/index.post.ts (1 hunks)
  • apps/web-app/server/api/post/list.get.ts (1 hunks)
  • apps/web-app/server/api/print/id/[printId].delete.ts (1 hunks)
  • apps/web-app/server/api/print/id/[printId].patch.ts (1 hunks)
  • apps/web-app/server/api/print/index.post.ts (1 hunks)
  • apps/web-app/server/api/print/list.get.ts (1 hunks)
  • apps/web-app/server/api/product/id/[productId]/image.post.ts (1 hunks)
  • apps/web-app/server/api/product/id/[productId]/index.delete.ts (1 hunks)
  • apps/web-app/server/api/product/id/[productId]/index.patch.ts (1 hunks)
  • apps/web-app/server/api/product/index.post.ts (1 hunks)
  • apps/web-app/server/api/product/list.get.ts (1 hunks)
  • apps/web-app/server/api/product/tag/list.get.ts (1 hunks)
  • apps/web-app/server/api/product/variant/id/[variantId]/index.delete.ts (1 hunks)
  • apps/web-app/server/api/product/variant/id/[variantId]/index.patch.ts (1 hunks)
  • apps/web-app/server/api/product/variant/index.post.ts (1 hunks)
  • apps/web-app/server/api/product/variant/tag/list.get.ts (1 hunks)
  • apps/web-app/server/api/task/id/[taskId]/complete.post.ts (1 hunks)
  • apps/web-app/server/api/task/id/[taskId]/focus.delete.ts (1 hunks)
  • apps/web-app/server/api/task/id/[taskId]/focus.post.ts (1 hunks)
  • apps/web-app/server/api/task/id/[taskId]/index.delete.ts (1 hunks)
  • apps/web-app/server/api/task/id/[taskId]/index.patch.ts (1 hunks)
  • apps/web-app/server/api/task/index.post.ts (1 hunks)
  • apps/web-app/server/api/task/list/completed.get.ts (1 hunks)
  • apps/web-app/server/api/task/list/id/[listId].delete.ts (1 hunks)
  • apps/web-app/server/api/task/list/id/[listId].patch.ts (1 hunks)
  • apps/web-app/server/api/task/list/index.get.ts (1 hunks)
  • apps/web-app/server/api/task/list/index.post.ts (1 hunks)
  • apps/web-app/server/api/user/id/[userId]/complete.post.ts (1 hunks)
  • apps/web-app/server/api/user/id/[userId]/image.post.ts (1 hunks)
  • apps/web-app/server/api/user/id/[userId]/index.get.ts (1 hunks)
  • apps/web-app/server/api/user/id/[userId]/index.patch.ts (1 hunks)
  • apps/web-app/server/api/user/id/[userId]/online.post.ts (1 hunks)
  • apps/web-app/server/api/user/list/staff.get.ts (1 hunks)
  • apps/web-app/server/plugins/01.database.ts (1 hunks)
  • apps/web-app/server/tasks/kitchen/rating-update.ts (1 hunks)
  • apps/web-app/server/tasks/task/auto-create.ts (1 hunks)
  • apps/web-app/server/utils/permission.ts (1 hunks)
  • apps/web-app/stores/chat.ts (1 hunks)
  • apps/web-app/stores/checkout.ts (1 hunks)
  • apps/web-app/stores/client.ts (1 hunks)
  • apps/web-app/stores/menu.ts (1 hunks)
  • apps/web-app/stores/notification.ts (1 hunks)
  • apps/web-app/stores/partner.ts (1 hunks)
  • apps/web-app/stores/post.ts (1 hunks)
  • apps/web-app/stores/product.ts (1 hunks)
  • apps/web-app/stores/task.ts (1 hunks)
  • apps/web-app/stores/user.ts (1 hunks)
  • apps/web-app/types/index.ts (1 hunks)
  • apps/web-parser/package.json (2 hunks)
⛔ Files not processed due to max files limit (29)
  • apps/web-parser/server/plugins/01.database.ts
  • apps/web-parser/server/tasks/yandex/update-data.ts
  • apps/web-storefront/app/components/ProductImage.vue
  • apps/web-storefront/app/components/cart/DeliveryMethodSwitch.vue
  • apps/web-storefront/app/components/checkout/Item.vue
  • apps/web-storefront/nuxt.config.ts
  • apps/web-storefront/package.json
  • apps/web-storefront/server/api/channel/index.get.ts
  • apps/web-storefront/server/api/checkout/add.post.ts
  • apps/web-storefront/server/api/checkout/id/[checkoutId].get.ts
  • apps/web-storefront/server/api/checkout/index.get.ts
  • apps/web-storefront/server/api/checkout/index.patch.ts
  • apps/web-storefront/server/api/checkout/item/[itemId].post.ts
  • apps/web-storefront/server/api/city/list.get.ts
  • apps/web-storefront/server/api/health/index.get.ts
  • apps/web-storefront/server/api/kitchen/distance.get.ts
  • apps/web-storefront/server/api/menu/index.get.ts
  • apps/web-storefront/server/plugins/01.database.ts
  • apps/web-storefront/stores/channel.ts
  • apps/web-storefront/stores/checkout.ts
  • apps/web-storefront/stores/city.ts
  • apps/web-storefront/stores/menu.ts
  • apps/web-storefront/types/index.ts
  • docker/web-app/Dockerfile
  • docker/web-storefront/Dockerfile
  • package.json
  • packages/database/package.json
  • packages/geo-database/package.json
  • packages/ui/package.json
🔇 Additional comments (84)
apps/web-parser/package.json (2)

2-2: Namespace rename looks correct
Changing the name field to @roll-stack/web-parser aligns with the repo-wide migration and keeps package metadata consistent.


12-12: No leftover @sushi-atrium/database references found
Ripgrep across the repository returned zero matches, confirming the dependency rename is complete.

apps/web-app/app/components/TaskCard.vue (1)

123-123: Import scope updated – LGTM
Task now comes from @roll-stack/database; no additional changes needed.

apps/web-app/server/api/menu/category/id/[categoryId]/index.patch.ts (1)

1-1: Repository import path updated correctly
No further changes required for this handler.

apps/web-app/server/api/post/index.post.ts (1)

1-1: Repository import path updated correctly
No functional impact on the endpoint.

apps/web-app/server/api/post/comment/id/[commentId]/index.delete.ts (1)

1-1: Package rename verification complete

  • No lingering imports of @sushi-atrium/database were found.
  • The new @roll-stack/database dependency is declared in every package.json under
    • apps/web-storefront/package.json
    • apps/web-parser/package.json
    • apps/web-app/package.json

All requested checks have passed; no further action is required.

apps/web-app/server/tasks/task/auto-create.ts (1)

1-1: ✅ @roll-stack/database migration is fully wired-up

All legacy @sushi-atrium/database imports and aliases have been removed, and every workspace that actually imports the new package declares it:

• No @sushi-atrium/database imports anywhere in source or configs
• TS path mappings, Nuxt/Webpack/Nitro aliases cleaned up across all configs
• Workspaces importing @roll-stack/database (web-app, web-parser, web-storefront) list it in their package.json

No further action required here.

apps/web-app/server/api/menu/category/id/[categoryId]/product.delete.ts (1)

1-1: Same namespace-migration caveat applies

Ensure every serverless/runtime context ships the renamed package and no old alias lingers. Execute the verification script above from repo root after install.

apps/web-app/server/api/product/variant/index.post.ts (1)

1-1: Dependency check for new database scope

The handler compiles only if @roll-stack/database is resolvable by both the Nitro server and your unit-test runner. Double-check lock-files and CI images.

apps/web-app/server/tasks/kitchen/rating-update.ts (1)

1-1: Import path updated – verify CI image caching

If the Docker / build image pre-installs the old scoped package, make sure cache is busted so the new package is installed, otherwise runtime MODULE_NOT_FOUND will surface only after deploy.

apps/web-app/app/components/TaskPopover.vue (1)

31-31: Check Volar / TS path mapping for .vue script setup

Volar sometimes requires explicit paths to resolve non-npm workspace packages.
If you see “cannot find module '@roll-stack/database'” in IDE, add/update:

// tsconfig.json
{
  "compilerOptions": {
    "paths": {
      "@roll-stack/database": ["packages/database/src/index.ts"]
    }
  }
}

Otherwise good to go.

apps/web-app/app/pages/post/index.vue (1)

44-44: No stale imports found – a repo-wide search confirms zero occurrences of @sushi-atrium/database.
✅ No further action needed.

apps/web-app/app/pages/print/index.vue (1)

151-151: Consistent rename confirmed – double-check build/tsconfig paths

The switch to @roll-stack/database is consistent with the migration plan. Make sure tsconfig.json / Nuxt alias configs include the new package so type resolution still works.

apps/geo-vault/server/api/geo/object-parents.get.ts (1)

2-2: Backend import updated – verify package is published

@roll-stack/geo-database is referenced for the repository layer. Ensure the package is published (or available in the workspace) before deploying to avoid runtime module-not-found errors.

apps/geo-vault/server/api/geo/houses.get.ts (1)

2-2: Rename applied – confirm no mixed namespaces

Looks correct. Mixing the old and new scopes in the same service can cause duplicate instance issues; validate other files under apps/geo-vault also migrated.

apps/web-app/app/pages/product/index.vue (1)

166-166: Frontend import adjusted – LGTM

The import path now aligns with the new namespace. No further action required besides the global search for missed occurrences noted earlier.

apps/web-app/server/api/user/id/[userId]/complete.post.ts (1)

1-1: Confirm server bundle picks up the renamed package

Server-side code relies on repository from @roll-stack/database.
Double-check that the Node runtime/container image includes the new package version (or symlink) to avoid runtime MODULE_NOT_FOUND.

apps/web-app/app/components/PostImage.vue (1)

25-25: LGTM – import path updated correctly
No issues spotted.

apps/web-app/app/components/ProductImage.vue (1)

28-28: LGTM – import path updated correctly
No issues spotted.

apps/web-app/app/components/form/UpdatePost.vue (1)

129-129: Namespace rename applied correctly

Import path switched from @sushi-atrium/database to @roll-stack/database, matching the new package scope. No other code impact.

apps/web-app/server/api/print/list.get.ts (1)

1-1: Import path update looks good

The repository import now points at the new @roll-stack/database package; function call remains intact.

apps/web-app/app/components/PartnerCard.vue (1)

43-43: Type import updated successfully

Partner type now sourced from the renamed package. No further action needed.

apps/web-app/app/components/ClientReviewCard.vue (1)

63-63: Consistent package rename

ClientReview type import adjusted to new namespace; rest of component unchanged.

apps/web-app/stores/client.ts (1)

1-1: Store type import aligned with new scope

ClientReview now pulled from @roll-stack/database; store logic unaffected.

apps/web-app/app/pages/product/[productId]/usage.vue (1)

113-113: All @sushi-atrium/database imports replaced
No occurrences of @sushi-atrium/database were found in the repository after running the scan. The migration to @roll-stack/database is complete—approving these changes.

apps/web-app/app/components/FeedbackPointsBlock.vue (1)

43-43: Import path updated – no issues found
The type import was correctly switched to @roll-stack/database.

apps/web-app/server/api/menu/category/id/[categoryId]/product.post.ts (1)

1-1: Import namespace migration validated
repository now points to @roll-stack/database. No other changes required here.

apps/web-app/server/api/post/id/[postId]/index.patch.ts (1)

1-1: Import namespace migration validated
Path switched to the new scope correctly.

apps/web-app/server/api/chat/index.post.ts (1)

1-1: Import namespace migration validated
No further action needed for the path change.

apps/web-app/stores/user.ts (1)

1-1: Namespace rename looks correct.

Nothing else to flag on the import itself; downstream type-only consumers will not be affected.

apps/web-app/app/components/UserPopover.vue (1)

42-42: Import updated – LGTM.
Pure namespace swap, no additional concerns.

apps/web-app/server/api/task/list/id/[listId].patch.ts (1)

1-1: Import path updated – looks good.

apps/web-app/server/api/post/id/[postId]/comment.post.ts (1)

1-1: Import path updated – no issues.

apps/web-app/stores/partner.ts (1)

1-1: Import rename verified.

No further action required here.

apps/web-app/app/components/StaffCard.vue (1)

39-39: All references to @roll-stack/database are correctly updated

  • Each application’s package.json (apps/web-app, web-parser, web-storefront) lists "@roll-stack/database": "workspace:*".
  • No residual @sushi-atrium imports remain in the codebase.
  • There are no custom TypeScript paths or Nuxt alias entries for the old scope, so nothing else to migrate.

No further action required here.

apps/web-app/server/utils/permission.ts (1)

3-3: Rename applied consistently – verify runtime resolution.

No functional change here; just be certain the new package exports the same repository API to avoid runtime breakage.

apps/web-app/server/api/product/id/[productId]/index.patch.ts (1)

1-1: Import path updated — LGTM.

Nothing else changed; compilation should succeed once the new package is available.

apps/geo-vault/server/plugins/01.database.ts (1)

2-2: Check dependency graph for @roll-stack/geo-database.

Same comment as earlier: ensure the renamed package is declared in apps/geo-vault/package.json and published, otherwise Nitro plugin startup will fail.

apps/web-app/server/api/task/id/[taskId]/focus.delete.ts (1)

1-1: Consistent namespace migration – looks correct.

No further issues spotted.

apps/web-app/server/api/menu/category/index.post.ts (1)

2-2: Confirmation: No legacy imports or missing dependencies found
All workspace package.json files include @roll-stack/database, and there are no remaining @sushi-atrium/database references.

apps/web-app/server/api/post/id/[postId]/like.delete.ts (1)

1-1: LGTM – namespace updated
Nothing else changed in this file; the new import path is consistent with the repo-wide rename.

apps/web-app/server/api/product/id/[productId]/index.delete.ts (1)

1-1: LGTM – namespace updated

No further issues spotted.

apps/web-app/server/api/product/index.post.ts (1)

2-2: LGTM – namespace updated

Everything else remains unchanged.

apps/web-app/server/api/product/variant/id/[variantId]/index.patch.ts (1)

1-1: LGTM – namespace updated

No additional concerns.

apps/web-app/server/api/task/id/[taskId]/focus.post.ts (1)

1-1: Confirmed: No residual @sushi-atrium imports

Ran rg -n "@sushi-atrium/" across the entire repo and found no matches. All namespace updates are in place—this is ready to merge.

apps/web-app/server/api/print/id/[printId].delete.ts (1)

1-1: Import namespace update verified—ready to merge

  • No remaining @sushi-atrium/database imports found.
  • @roll-stack/database is declared in all relevant package.json files (apps/web-app, apps/web-storefront, apps/web-parser, and packages/database).

Approve and merge.

apps/web-app/server/api/chat/my/index.get.ts (1)

1-1: Import rename looks correct – verify path mapping

The switch to @roll-stack/database aligns with the namespace migration.
Please double-check that the package is present in the workspace package.json and that any paths/alias configuration (e.g., tsconfig.json, vite.config.ts) has been updated to avoid unresolved-module errors at build or CI time.

apps/web-app/server/api/notification/my.get.ts (1)

1-1: Consistent namespace update – no further issues

Import path updated to the new scope; no functional impact detected.
Ensure dependency & path aliases are synchronised across all packages just like in other files.

apps/web-app/server/api/payment/method/list.get.ts (1)

1-1: LGTM for payment repository import

Change mirrors the global rename; no other code touched.

apps/web-app/server/api/user/id/[userId]/index.get.ts (1)

1-1: Import updated – remember to update tests

Import rename is fine. If you have integration / unit tests mocking the previous package name, update those fixtures to the new scope to keep the test suite green.

apps/geo-vault/server/api/geo/objects.get.ts (1)

2-2: Geo-database namespace migration acknowledged

Import now points to @roll-stack/geo-database. Looks good and consistent with other files.
Make sure the monorepo dependency graph (e.g., pnpm workspace, turborepo pipeline) is refreshed so this package is built/published under the new scope before deploying.

apps/geo-vault/server/api/geo/house-parents.get.ts (1)

2-2: Dependency resolution verified

  • ✅ No references to the old @sushi-atrium/geo-database scope remain.
  • ✅ The new @roll-stack/geo-database package is declared in both apps/geo-vault/package.json (line 16) and as the package name in packages/geo-database/package.json.

No further action required.

apps/web-app/server/api/product/tag/list.get.ts (1)

1-1: Rename acknowledged

No functional impact; the handler remains unchanged.

apps/web-app/server/api/task/id/[taskId]/index.delete.ts (1)

1-1: Namespace switch okay – verify monorepo publish order

@roll-stack/database must be published before this app is deployed; otherwise cold-start errors will occur.

apps/web-app/server/api/menu/category/id/[categoryId]/index.delete.ts (1)

1-1: Import path updated correctly

Looks good. No further issues spotted.

apps/web-app/server/api/post/id/[postId]/index.delete.ts (1)

1-1: All stale imports removed — alias coverage confirmed

  • Ran rg --line-number '@sushi-atrium/' --glob '*.ts' --glob '*.vue' → ✅ no matches
  • No remaining references to the old @sushi-atrium scope

Alias migrations look complete across the repo.

apps/web-app/stores/menu.ts (1)

1-1: LGTM – menu store now references new database package

No additional changes needed.

apps/web-app/stores/chat.ts (1)

1-1: Import path updated successfully

Looks good and consistent with the namespace migration.

apps/web-app/stores/post.ts (1)

1-1: Post store import updated – OK

The change compiles fine; no further action required.

apps/web-app/stores/product.ts (1)

1-1: Product store import path corrected

Change is correct and matches the new package scope.

apps/web-app/app/components/CheckoutItem.vue (1)

30-30: No residual @sushi-atrium imports found—please manually confirm

Ran:

rg --line-number --no-heading '@sushi-atrium'

Result: no matches.

As a final safety check, please scan for any stray @sushi-atrium references before merging.

apps/web-app/stores/task.ts (1)

1-1: Import namespace updated correctly

Nothing else changed in this store; the new type source @roll-stack/database is consistent with the migration.

apps/web-app/server/api/task/id/[taskId]/index.patch.ts (1)

1-2: Repository + types now pulled from new scope

Both the type import and the repository import point to @roll-stack/database. Behaviour and runtime contracts remain unchanged.

apps/web-app/server/api/user/id/[userId]/index.patch.ts (1)

1-1: Repository import path updated

No functional change; handler continues to use the same repository API. LGTM.

apps/web-app/server/plugins/01.database.ts (1)

2-2: Namespace rename looks correct – confirm new package is declared

Import updated to @roll-stack/database, matching the re-scoped namespace. Please verify that @roll-stack/database is now listed in every affected package.json (dependencies or devDependencies) so CI/CD doesn’t fail on missing modules.

apps/web-app/server/api/task/list/id/[listId].delete.ts (1)

1-1: Import path update LGTM

The repository import now points to the new scope; no other changes required.

apps/web-app/server/api/product/variant/tag/list.get.ts (1)

1-1: Consistent rename – no issues spotted

Import path switch aligns with the rest of the migration.

apps/web-app/server/api/user/id/[userId]/image.post.ts (1)

1-3: Both type & runtime imports correctly re-scoped

Types (MediaItemDraft) and runtime repository import now come from the new package. Double-check that type exports remain identical in the re-published package to avoid TS errors down the line.

apps/web-app/app/pages/head/task/index.vue (1)

209-209: Type import updated – all good

Task type source switched to @roll-stack/database; no further action needed.

apps/web-app/server/api/health/index.get.ts (1)

1-1: No lingering @sushi-atrium/ imports detected

Verified by running:

rg --no-heading -n "@sushi-atrium/" --glob "*.{ts,tsx,js,jsx}"

– no matches found. The import path is correct and the migration to @roll-stack/* is complete.

apps/web-app/server/api/checkout/list.get.ts (1)

1-1: Import namespace updated – LGTM

Nothing else changed; handler logic unaffected.

apps/web-app/server/api/post/id/[postId]/image.post.ts (1)

1-4: Coherent rename for both type and repository imports

Change is self-contained, matches the project-wide rename.
Confirm the new path is added to path aliases (tsconfig / vite / jest) to avoid resolution issues in downstream tooling.

apps/web-app/server/api/product/id/[productId]/image.post.ts (1)

1-4: Consistent namespace switch

No functional impact detected. Ensure package.json/workspace dependencies list @roll-stack/database so production image picks it up.

apps/web-app/nuxt.config.ts (1)

2-2: extends updated → make sure package is installed & version-pinned

Nuxt will fail fast if @roll-stack/ui isn’t present or the version is incompatible with other plugins.
Double-check package.json and lockfile, then run a fresh install.

apps/web-app/app/components/ProductTagsBlock.vue (1)

15-15: Import namespace updated – double-check TS path aliases

The switch to @roll-stack/database looks correct. Make sure tsconfig.json / vite.config.ts path-alias entries are updated accordingly so the IDE and build pipeline resolve the new package without fallback to the old scope.

apps/web-app/stores/checkout.ts (1)

1-1: LGTM – checkout store types now point at new package

The type-only import was correctly migrated. No other logic touched, compilation should stay unaffected.

apps/geo-vault/server/api/address/index.post.ts (1)

2-2: Repository import renamed – verify package publish

The reference to @roll-stack/geo-database aligns with the namespace migration. Please ensure the package has been published to your registry and CI/CD pipelines pull the correct version before merging.

apps/web-app/server/api/client/review/list.get.ts (1)

1-1: Client-review API import path updated

Nothing else changed; safe to merge.

apps/web-app/server/api/post/list.get.ts (1)

1-1: Post list API import path updated

Looks good.

apps/web-app/server/api/product/list.get.ts (1)

1-1: Import scope update looks good – verify that the alias exists.

No issues with the code itself.
Please ensure @roll-stack/database is resolvable in the workspace (tsconfig → paths / package.json workspaces) so downstream builds don’t break.

apps/web-app/server/api/menu/list.get.ts (1)

1-1: LGTM – same note on path resolution.

Import path change is correct; just confirm the new scope is mapped everywhere to avoid type-checker errors.

apps/web-app/server/api/kitchen/list.get.ts (1)

1-1: Import path renamed – confirm workspace mapping.

Same comment as above: make sure @roll-stack/database resolves to avoid runtime/compile surprises.

apps/geo-vault/package.json (1)

2-2: Rename & dependency scope LGTM – workspace availability verified

File: apps/geo-vault/package.json
Lines: 2-2, 16-16

  "name": "@roll-stack/geo-vault",

Confirmed that @roll-stack/geo-database is declared in packages/*/package.json, so pnpm install will succeed. No further action required.

apps/web-app/package.json (1)

2-2: All old-scope imports removed – migration complete

Confirmed by running:

rg --color never '@sushi-atrium/' apps/web-app

No occurrences found in the entire apps/web-app directory. Ready to merge.

@@ -1,4 +1,4 @@
import { repository } from '@sushi-atrium/database'
import { repository } from '@roll-stack/database'
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Import path renamed – verify package availability

Good catch on updating the scope. Please double-check that @roll-stack/database is now published/linked in every package.json (root + workspaces) and that any TS path aliases (tsconfig.json, eslint, Vite/Nitro config) were updated; otherwise the build will fail at runtime/CI.


🏁 Script executed:

#!/bin/bash
# Ensure every workspace declares the new dependency
fd package.json | xargs jq -r '.name + " -> " + (.dependencies["@roll-stack/database"] // .devDependencies["@roll-stack/database"] // "MISSING")'

Length of output: 411


Action Required: Add missing @roll-stack/database dependencies

The workspace scan shows that several packages don’t declare the new @roll-stack/database dependency and will break on install:

• @roll-stack/geo-vault – MISSING
• roll-stack (root) – MISSING
• @roll-stack/database (self) – MISSING
• @roll-stack/geo-database – MISSING
• @roll-stack/ui – MISSING

Please add @roll-stack/database to the dependencies of each of the above package.json files. The other workspaces (@roll-stack/web-app, @roll-stack/web-parser, @roll-stack/web-storefront) are already referencing it as workspace:*.

Also verify that any TypeScript path aliases (in tsconfig.json), ESLint settings, and Vite/Nitro configs have been updated to reflect the new package name, so that imports continue to resolve correctly.

🤖 Prompt for AI Agents
In the package.json files of @roll-stack/geo-vault, roll-stack (root),
@roll-stack/database, @roll-stack/geo-database, and @roll-stack/ui, add
@roll-stack/database as a dependency to ensure proper installation.
Additionally, verify and update TypeScript path aliases in tsconfig.json, ESLint
configurations, and Vite/Nitro settings to correctly resolve imports from the
new package name.


<script setup lang="ts">
import type { Kitchen } from '@sushi-atrium/database'
import type { Kitchen } from '@roll-stack/database'
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify migration completeness & dependency availability

@roll-stack/database compiles only if

  1. the package (or workspace) truly exists in package.json/lock-files, and
  2. every lingering @sushi-atrium/ reference has been removed.

Run a quick sweep to catch any stragglers:

Expect zero hits; otherwise update the leftovers or add an alias in the build config.


🏁 Script executed:

#!/usr/bin/env bash
# Find unreplaced occurrences of the old namespace
rg --color never --line-number --fixed-strings "@sushi-atrium" || true

Length of output: 69


🏁 Script executed:

#!/usr/bin/env bash
# Verify that @roll-stack/database is declared in package.json and/or lock files

# 1. Check package.json
echo "== Checking package.json for @roll-stack/database =="
if [ -f package.json ]; then
  grep -R '"@roll-stack/database"' -n package.json \
    && echo "→ Found in package.json" \
    || echo "→ Not found in package.json"
else
  echo "→ package.json not found"
fi

# 2. Check common lockfiles
for lock in yarn.lock package-lock.json pnpm-lock.yaml; do
  if [ -f "$lock" ]; then
    echo "== Checking $lock for @roll-stack/database =="
    grep -R "@roll-stack/database" -n "$lock" \
      && echo "→ Found in $lock" \
      || echo "→ Not found in $lock"
  fi
done

Length of output: 840


Add @roll-stack/database as a direct dependency

The import in apps/web-app/app/components/KitchenCard.vue relies on @roll-stack/database, but it isn’t declared in your package.json—it only appears transitively in pnpm-lock.yaml. This can lead to compilation or runtime surprises if the lockfile changes.

• Update package.json under dependencies (or your workspace config) to include @roll-stack/database at the matching version.
• Verify the version aligns with what’s locked in pnpm-lock.yaml (lines ~297, 340, 359).
• No @sushi-atrium references were found in the repo.

Example change:

 // package.json
 {
   "dependencies": {
     // …existing deps
+    "@roll-stack/database": "^<version>"
   }
 }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
import type { Kitchen } from '@roll-stack/database'
// package.json
{
"dependencies": {
// …existing deps
+ "@roll-stack/database": "^<version>"
}
}
🤖 Prompt for AI Agents
In apps/web-app/app/components/KitchenCard.vue at line 16, the import of
@roll-stack/database is used but not declared as a direct dependency. To fix
this, add @roll-stack/database to the dependencies section of the package.json
file in the apps/web-app directory (or the relevant workspace config) with the
exact version matching the one found in pnpm-lock.yaml around lines 297, 340, or
359. This ensures consistent and reliable dependency resolution during
compilation and runtime.

@sonarqubecloud
Copy link
Copy Markdown

@hmbanan666 hmbanan666 merged commit edfcd1b into main Jul 17, 2025
6 checks passed
@hmbanan666 hmbanan666 deleted the rename branch July 17, 2025 14:15
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.

1 participant