name: configure-plugin-navigation description: Configure erxes frontend plugin navigation, settings navigation, icons, module entries, widget declarations, and config paths. Use when changing src/config.tsx or plugin navigation surfaces.
Skill: Configure Plugin Navigation
Workflow
- Open the plugin's
src/config.tsxand nearby plugin config files. - Reuse the plugin's existing
IUIConfigshape:name,path,icon,navigationGroup,modules, andwidgetswhen present. - Use icons from
@tabler/icons-reactand keep icon naming consistent with nearby config files. - Add module entries only when the module should appear in app navigation or settings navigation.
- Add
relationWidgetsor floating widgets only when the plugin exposes and implements those widget surfaces. - Keep paths aligned with route registration and Module Federation exposes.
- Run
pnpm nx lint <plugin>andpnpm nx build <plugin>for code changes.
Important
- Do not add plugin-specific navigation or widgets in
frontend/core-ui. - Do not use
IconSandboxas a final icon unless the surrounding plugin is intentionally still placeholder-quality. - Check
module-federation.config.tsbefore adding widget or module config that depends on a remote expose. - Preserve
hasSettings, relation widget, and floating widget behavior used by nearby plugin config files.