Conversation
MUSE-1194 fix vite dev mode issue
MUSE-1223 add integration guides for Muse ui plugins
MUSE-1243 added MSP builder
MUSE-1252 added MSP mgmt APIs
MUSE-1251 added sync latest API
MUSE-1253 add msp cli
MUSE-1252 add msp registry schema
MUSE-1244 upgrade tool in muse-dev-utils
MUSE-1265 sdk upgrade
MUSE-1280 update to latest antd, react
MUSE-1269 - Remove approval for prod env message
MUSE-1312 ensure lib plugin load sequence
MUSE-1310 add msp meta to plugin release.
MUSE-1309 validate msp when deployment
MUSE-1331 show MSP mismatch error when deploy validation
MUSE-1308 fix vanilla vite plugin
MUSE-1308 allow config msp for app and env
MUSE-1333 msp config ui
MUSE-1336 fix lib plugin build performance issue in watch mode
MUSE-1290 msp mgmt ui
MUSE-1359, MUSE-1359, MUSE-1360, MUSE-1361, MUSE-1362 upgrade examples plugin to msp2606
MUSE-1391 antd v5 -> v6 migration
MUSE-1418 fix sub app
MUSE-1425 escape app title
## Summary Fixes the following React warning produced when rendering menus with `activeMatch`: ```text Warning: React does not recognize the `activeMatch` prop on a DOM element. If you accidentally passed it from a parent component, remove it from the DOM element. ``` ## Root cause `MetaMenu` uses the Muse-specific `activeMatch` property to calculate the active menu keys. After evaluating it, the original menu-item objects are passed to Ant Design unchanged. Ant Design/rc-menu does not recognize `activeMatch` as a menu property and forwards it to the underlying `<li>`, which triggers the React warning. ## Fix Before passing items to Ant Design, `MetaMenu` now recursively clones the menu tree and removes `activeMatch`. The original internal items are retained for route matching, so existing active-menu behavior is unchanged. Recursive sanitization covers both top-level submenu items and nested children. ## Testing - Added regression coverage for parent and nested menu items containing `activeMatch`. - Verified that unsanitized items produce the React warning while sanitized items do not. - Confirmed the `muse-lib-antd` production build succeeds.
MUSE-1428 Add environment variable security warning and pre-check before saving
Prevent activeMatch from being forwarded to menu DOM elements
Sdk upgrade dev
add new plugin template
Render untrusted boot errors as text, validate plugin name/type/version, and only apply forcePlugins in local/dev or Muse e2e. Co-authored-by: Cursor <cursoragent@cursor.com>
Prevent DOM XSS in muse-boot-default error UI and restrict forcePlugins.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.