feat: Open international professional features

[lan-yonghui]

No description provided.

[f2c-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[wanghe-fit2cloud]

The provided code appears to be part of a Vue.js application using the Element Plus UI library. Here's an assessment of the code:

Potential Issue

The condition if (menuItem.path === '/xpack') is inside the loop that processes each MenuItem within the MenuList. This means it will process all children regardless of whether their path starts with /xpack/. If there are children at other paths under /xpack, they may become inaccessible depending on the logic used later.

Suggestion

Consider refactoring this loop structure so that you only apply the filtering logic when a specific condition (e.g., checking for sub-paths beneath /xpack) occurs, rather than processing all items every time.

Here’s one possible way to refactor it:

// Initialize filtered menu list directly outside the main loop
let filteredMenuList: RouteRecordRaw[] = [];

menuStore.menuList.forEach((item) => {
    // Process parent item
    let menuItem = JSON.parse(JSON.stringify(item));
    if (menuItem.path === "/xpack") {
        // Determine which parts should remain visible based on user settings
        filteredMenuList.push(menuItem); // Add current item since it matches '/xpack'
        
        // Apply visibility filter to child menu options
        menuItem.children = menuItem.children.filter(child => !child.path.includes("/xpack/alert"));
        
        // Recursively process the child menu
        recursivelyFilterChildMenuItems(filteredMenuList, child);
    } else {
        // Directly add non-menu-item nodes to final result set.
        rstMenuList.push(menuItem);
    }
});

function recursivelyFilterChildMenuItems(parentList: RouteRecordRaw[], targetMenuItem: RouteRecordRaw) {
    // ... Existing code remains same ...
}

By doing this, you ensure that each MenuItem is processed only once, improving efficiency when dealing with nested structures.

---

Make sure this change aligns fully with your application's requirements and architecture before implementing it!

[wanghe-fit2cloud]

The provided patch seems mostly correct overall, but there is one change that needs consideration:

• The link URLs for LxWare have been updated to different domain links ('lxware.cn' vs '1panel.hk'). This could indicate intentional changes based on internationalization context not captured in the knowledge cutoff information.

However, from a functional standpoint, updating the links without further context about internationalization implications does not pose major issues. Here's an outline of what each line does, which helps verify their correctness:

@@ -5,8 +5,8 @@
         <el-link type="primary" :underline="false" @click="toForum">
             <span class="font-normal">{{ $t('setting.forum') }}</span>
         </el-link>
-        <!-- Vertical divider if not international -->
-        <el-divider direction="vertical" v-if="!globalStore.isIntl" />
+        <!-- Vertical divider regardless of global store state -->
+        <el-divider direction="vertical" />

@@ -17,7 +17,7 @@
                 </el-button> -- Adjusting this comment as requested --

@@ -125,6 +125,8 @@ const handleClose = () => {
     ...
 };

+const toLxware = () => {
+    // Updated logic ensuring only appropriate URL opens depending globally configured locale
+
     ...
 };

These modifications align with standard practices in JavaScript and TypeScript development while making some minor syntactic adjustments like removing unnecessary spaces around operators (=). If you have additional requirements such as testing or validation, let me know!

[wanghe-fit2cloud]

Your code has several improvements, but there are a few areas where you can optimize it further:

1. Remove Unnecessary Variable Declaration: The globalStore variable is only used once and assigned directly within the condition, so you can simplify this line to assign it on use.

2. Use of Template Literals: If you need to concatenate strings dynamically, using template literals is more concise and readable.

import i18n from '@/lang';
// Removed: import { GlobalStore } from '@/store';

<script lang="ts" setup>
const globalStore: ReturnType<typeof import('@/store')> = await import('@/store').then(m => m.GlobalStore());

const buttons = [
    {
        text: 'Settings.',
        iconText: '<span aria-hidden="true">fas fa-cog</span>',
        path: '/settings/account',
    },
    ...[
        // other menu items remain unchanged...
    ],
];

if (globalStore.isIntl) {
    buttons.splice(4, 1); // Assuming the index is correct; adjust if necessary.
}
</script>

3. Avoid Redundant Imports: Ensure that all imports needed at the top level are included.

Here's the optimized code with these changes:

import i18n from '@/lang';
import GlobalStore from '@/store';

const globalStore = new GlobalStore();

const buttons = [
    {
        text: 'Settings.',
        iconText: '<span aria-hidden="true">fas fa-cog</span>',
        path: '/settings/account',
    },
    // ... rest of button configurations ...
];

if (globalStore.isIntl) {
    buttons.splice(4, 1); // Adjust the index based on your logic needs.
}

<template>
    <!-- Your template content here -->
</template>

<script lang="ts">
export default defineComponent({
    components: {},
});
</script>

<style scoped>
/* Your styles go here */
</style>

By making these adjustments, your code will be cleaner, more efficient, and easier to maintain. Make sure to test thoroughly after applying these changes to ensure compatibility and functionality.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wanghe-fit2cloud]

/lgtm

[wanghe-fit2cloud]

/approve

[f2c-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wanghe-fit2cloud

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [wanghe-fit2cloud]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment