SideMenu Changes

[ammb-123]

Description

Flag is added to on/off the side menu in the AI CORE app

Changes Made

ADMIN_ONLY_VIEW_MENU_BAR flag added

How to Test

Login to the AI core app ,user can able to view the ai core page without side menu bar and catalog items .
Config api has the adminOnlyViewMenuBarFlag : true

Notes

Uploading AdminUser_updated.docx…

[github-actions]

@CodiumAI-Agent /describe

[CodiumAI-Agent]

Title

SideMenu Changes

---

User description

Description

Flag is added to on/off the side menu in the AI CORE app

Changes Made

ADMIN_ONLY_VIEW_MENU_BAR flag added

How to Test

Login to the AI core app ,user can able to view the ai core page without side menu bar and catalog items .
Config api has the adminOnlyViewMenuBarFlag : true

Notes

Uploading AdminUser_updated.docx…

---

PR Type

Enhancement

---

Description

• Hide Filterbox when adminOnlyViewMenuBarFlag is true

• Require isEngineOperationAvailable('APP','add') for display

• Wrap Filterbox in combined visibility condition

---

Changes walkthrough 📝

	Relevant files
Enhancement	HomePage.tsx` Conditional `Filterbox` rendering                                                packages/client/src/pages/HomePage.tsx Added adminOnlyViewMenuBarFlag hide condition Integrated isEngineOperationAvailable('APP','add') check Wrapped Filterbox rendering in combined condition
Additional files	HomePage.tsx +12/-6

---

Need help?

Type /help how to ... in the comments thread for any questions about PR-Agent usage.

Check out the documentation for more information.

[github-actions]

@CodiumAI-Agent /review

[CodiumAI-Agent]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Conditional Rendering The nested flag and permission check (!configStore.store.config.adminOnlyViewMenuBarFlag && configStore.isEngineOperationAvailable(...)) could become hard to maintain or extend. Consider extracting this into a clearly named boolean or helper function for readability. {!configStore.store.config.adminOnlyViewMenuBarFlag && configStore.isEngineOperationAvailable( 'APP', 'add', ) && ( <Filterbox type={'APP'} onChange={(filters: Record<string, unknown>) => { setMetaFilters(filters); }} /> )} Default Flag Value If adminOnlyViewMenuBarFlag is undefined, the negation check may not behave as expected. Ensure the flag has a defined default (e.g., false) or explicitly coerce it to a boolean. {!configStore.store.config.adminOnlyViewMenuBarFlag && configStore.isEngineOperationAvailable( Missing Tests No tests were added or updated to cover the new flag logic. Consider adding unit or integration tests to validate both flag on/off states. {!configStore.store.config.adminOnlyViewMenuBarFlag && configStore.isEngineOperationAvailable( 'APP', 'add', ) && ( <Filterbox type={'APP'} onChange={(filters: Record<string, unknown>) => { setMetaFilters(filters); }} /> )}

[github-actions]

@CodiumAI-Agent /improve

[CodiumAI-Agent]

PR Code Suggestions ✨

Category	Suggestion	Impact
Possible issue	Add optional chaining guard Use optional chaining when reading nested properties to prevent runtime errors if store or config is undefined. This ensures the guard on adminOnlyViewMenuBarFlag won’t throw. packages/client/src/pages/HomePage.tsx [353-364] -{!configStore.store.config.adminOnlyViewMenuBarFlag && - configStore.isEngineOperationAvailable( - 'APP', - 'add', - ) && ( - <Filterbox - type={'APP'} - onChange={(filters: Record<string, unknown>) => { - setMetaFilters(filters); - }} - /> - )} +{ !configStore.store?.config?.adminOnlyViewMenuBarFlag && + configStore.isEngineOperationAvailable('APP', 'add') && ( + <Filterbox + type={'APP'} + onChange={(filters: Record<string, unknown>) => { + setMetaFilters(filters); + }} + /> + )} Suggestion importance[1-10]: 5 __ Why: Using optional chaining on configStore.store?.config prevents potential runtime errors when store or config is undefined without significantly altering behavior.	Low
General	Memoize visibility condition Extract the visibility condition into a useMemo or variable to avoid repeated calls and improve readability. Then use that variable in the JSX. packages/client/src/pages/HomePage.tsx [353-364] -{!configStore.store.config.adminOnlyViewMenuBarFlag && - configStore.isEngineOperationAvailable( - 'APP', - 'add', - ) && ( - <Filterbox - ... - /> - )} +const showFilterbox = useMemo( + () => !configStore.store.config.adminOnlyViewMenuBarFlag && + configStore.isEngineOperationAvailable('APP', 'add'), + [configStore.store.config.adminOnlyViewMenuBarFlag, configStore] +); +... +{showFilterbox && ( + <Filterbox + type={'APP'} + onChange={(filters: Record<string, unknown>) => setMetaFilters(filters)} + /> +)} Suggestion importance[1-10]: 5 __ Why: Extracting the filterbox visibility into useMemo improves readability and avoids recalculating the condition on each render.	Low
	Simplify onChange callback Pass setMetaFilters directly as the callback to avoid recreating the arrow function on each render and simplify the code. packages/client/src/pages/HomePage.tsx [360-362] -onChange={(filters: Record<string, unknown>) => { - setMetaFilters(filters); -}} +onChange={setMetaFilters} Suggestion importance[1-10]: 4 __ Why: Passing setMetaFilters directly reduces unnecessary arrow function creation and simplifies the JSX.	Low

[github-actions]

@CodiumAI-Agent /update_changelog

[CodiumAI-Agent]

Changelog updates: 🔄

2025-05-30 *

Added

• Add ADMIN_ONLY_VIEW_MENU_BAR flag and update side‐menu visibility logic

to commit the new content to the CHANGELOG.md file, please type:
'/update_changelog --pr_update_changelog.push_changelog_changes=true'