refactor: rename mokosuitesight → mokosuiteinsight for plugins, package, and DB tables (sibling to component rename #13) #17

New Issue

Open

opened 2026-07-07 06:21:16 +00:00 by jmiller · 0 comments

jmiller commented

2026-07-07 06:21:16 +00:00

Owner

Follow-up to the component element rename in PR #16 (which resolved #13 by renaming com_mokosuitesight → com_mokosuiteinsight).

PR #16 deliberately scoped out the sibling extensions to keep the component rename safe and self-contained. This issue tracks unifying the remaining mokosuitesight stem:

plg_system_mokosuitesight → plg_system_mokosuiteinsight (element/folder/namespace)
plg_webservices_mokosuitesight → plg_webservices_mokosuiteinsight (element/folder/namespace; also the public v1/mokosuitesight/... API URL prefix — the API contract)
pkg_mokosuitesight package element + <packagename> + pkg manifest filename
DB tables #__mokosuitesight_* → #__mokosuiteinsight_* — these are created and queried by plg_system_mokosuitesight, NOT the component, which is why PR #16 left them alone. Rename must move with the plugin, with a matching guarded/idempotent migration (mirror the component's Pkg_MokoSuiteInsightInstallerScript migration pattern and the ERP repo's approach in its PR #82).
PLG_*_MOKOSUITESIGHT language key prefixes

This mirrors how the ERP repo split its work: component element rename separately from the plugin/package rename (tracked there as #79).

Reference: component rename PR #16; ERP precedent MokoConsulting/MokoSuiteERP#82 and #79.

Follow-up to the component element rename in PR #16 (which resolved #13 by renaming `com_mokosuitesight` → `com_mokosuiteinsight`). PR #16 **deliberately scoped out** the sibling extensions to keep the component rename safe and self-contained. This issue tracks unifying the remaining `mokosuitesight` stem: - [ ] `plg_system_mokosuitesight` → `plg_system_mokosuiteinsight` (element/folder/namespace) - [ ] `plg_webservices_mokosuitesight` → `plg_webservices_mokosuiteinsight` (element/folder/namespace; also the public `v1/mokosuitesight/...` API URL prefix — the API contract) - [ ] `pkg_mokosuitesight` package element + `<packagename>` + pkg manifest filename - [ ] **DB tables `#__mokosuitesight_*` → `#__mokosuiteinsight_*`** — these are created and queried by `plg_system_mokosuitesight`, NOT the component, which is why PR #16 left them alone. Rename must move with the plugin, with a matching guarded/idempotent migration (mirror the component's `Pkg_MokoSuiteInsightInstallerScript` migration pattern and the ERP repo's approach in its PR #82). - [ ] `PLG_*_MOKOSUITESIGHT` language key prefixes This mirrors how the ERP repo split its work: component element rename separately from the plugin/package rename (tracked there as #79). Reference: component rename PR #16; ERP precedent MokoConsulting/MokoSuiteERP#82 and #79.

Priority Medium

Type Feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoSuiteInsight#17