Skip to content

chore: move overview module out of admin folder#3860

Merged
emlimlf merged 2 commits intomainfrom
chore/move-overview-module
Feb 19, 2026
Merged

chore: move overview module out of admin folder#3860
emlimlf merged 2 commits intomainfrom
chore/move-overview-module

Conversation

@emlimlf
Copy link
Copy Markdown
Collaborator

@emlimlf emlimlf commented Feb 19, 2026

In this PR

Moved the overview module out of the admin module folder

Ticket

CM-982


Note

Medium Risk
Mostly mechanical import-path changes, but routing/import resolution can break at runtime/build time; at least one file still references the old overview types path.

Overview
Moves the Overview page out of the admin module by repointing the admin /overview route to @/modules/overview/pages/overview.vue and updating Overview components to use the new module-local relative imports.

This is primarily a path/refactor change, but there’s a likely leftover dependency: trend-display.vue still imports OverviewTrends from the old @/modules/admin/modules/overview/... path, which may break builds if the old module is removed.

Written by Cursor Bugbot for commit b78c032. This will update automatically on new commits. Configure here.

Signed-off-by: Efren Lim <elim@linuxfoundation.org>
@github-actions
Copy link
Copy Markdown
Contributor

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

  • feat: add user authentication (CM-123)
  • feat: add user authentication (IN-123)

Projects:

  • CM: Community Data Platform
  • IN: Insights

Please add a Jira issue key to your PR title.

3 similar comments
@github-actions
Copy link
Copy Markdown
Contributor

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

  • feat: add user authentication (CM-123)
  • feat: add user authentication (IN-123)

Projects:

  • CM: Community Data Platform
  • IN: Insights

Please add a Jira issue key to your PR title.

@github-actions
Copy link
Copy Markdown
Contributor

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

  • feat: add user authentication (CM-123)
  • feat: add user authentication (IN-123)

Projects:

  • CM: Community Data Platform
  • IN: Insights

Please add a Jira issue key to your PR title.

@github-actions
Copy link
Copy Markdown
Contributor

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

  • feat: add user authentication (CM-123)
  • feat: add user authentication (IN-123)

Projects:

  • CM: Community Data Platform
  • IN: Insights

Please add a Jira issue key to your PR title.

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

import LfIcon from '@/ui-kit/icon/Icon.vue';
import type { OverviewTrends } from '@/modules/admin/modules/overview/types/overview.types';
import { formatNumber } from '@/utils/number';
import type { OverviewTrends } from '@/modules/admin/modules/overview/types/overview.types';
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Stale import path for OverviewTrends in trend-display

High Severity

The OverviewTrends type import in trend-display.vue still points to the old path @/modules/admin/modules/overview/types/overview.types, but that file no longer exists — it was moved to @/modules/overview/types/overview.types.ts. Every other sibling file correctly uses the relative import ../../types/overview.types, but this one was missed during the move. This will break the build.

Fix in Cursor Fix in Web

@emlimlf emlimlf requested a review from gaspergrom February 19, 2026 07:29
@github-actions
Copy link
Copy Markdown
Contributor

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

  • feat: add user authentication (CM-123)
  • feat: add user authentication (IN-123)

Projects:

  • CM: Community Data Platform
  • IN: Insights

Please add a Jira issue key to your PR title.

@emlimlf emlimlf merged commit d031d74 into main Feb 19, 2026
13 checks passed
@emlimlf emlimlf deleted the chore/move-overview-module branch February 19, 2026 10:31
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.

2 participants