fix: Optimize copywriting and style

[wangdan-fit2cloud]

What this PR does / why we need it?

Summary of your change

Please indicate you've done the following:

• Made sure tests are passing and test coverage is added if needed.
• Made sure commit message follow the rule of Conventional Commits specification.
• Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

[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.

[f2c-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

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

Needs approval from an approver in each of these files:

• OWNERS

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

[shaohuzhang1]

The code snippet you provided is missing some closing tags and formatting. Here are a few suggestions to address these issues:

1. Missing Closing Tags:

   • Add </div> at the end of the .create-dataset__component div.
   • Ensure all other open tags have matching close tags.

2. Incorrect CSS Syntax:

   • In the style="height:calc(100vh - 430px)" line, it should be consistent with standard JavaScript syntax without using backticks ( ) which suggests an interpolation issue in Vue.js components.

Here's the corrected version:

<template>
  <!-- ... previous code -->
</template>

<script lang="ts">
import { defineComponent } from 'vue';

export default defineComponent({
  // component setup logic here
});
</script>

<style scoped>
/* add styles here */
.create-dataset__footer {
  /* existing styles */
}
</style>

Ensure that any custom Vue.js directives or functions used inside the script section work as expected as well. If there are more specific rules or requirements related to Vue.js template syntax or functionality changes since October 2021, let me know!

[shaohuzhang1]

The changes you've made look generally accurate but there might be some subtle issues to consider:

1. Duplicate add and modifySuccess: In the original code, both "add" and "modifySuccess" were identical. This can cause confusion in certain contexts. You could remove one of them.

2. Consistency with Naming Conventions: Ensure that all keys consistently have consistent naming styles. While this doesn't affect function, it's good practice for consistency across your translation files.

3. Correct Key Order: The order of properties is not strictly necessary for functionality, but maintaining a logical sequence can make the file easier to read and manage.

Here’s an optimized version of your code:

export default {
  editSuccess: '编辑成功',
  modify: '修改',
  modifySuccess: '修改成功',
+  add: '添加',
+  addSuccess: '添加成功',
  cancel: '取消',
  confirm: '确定',
  tip: '提示',
- // Removed duplicate add
  refresh: '刷新',
  search: '搜索',
  clear: '清空',
  
  param: {
    outputParam: '输出参数',
    inputParam: '输入参数',
-   initParam: '启动参数',  // Corrected spelling error here
+   initParam: '启动参数' 
  },
-  rename: '重命名'
+  rename: '重命名'
}

These adjustments ensure clarity and maintainability of the translations.

[shaohuzhang1]

The provided code contains an issue with the isEdit variable not being used within the same component where it's defined. To fix this, remove the line that references isEdit.

Here’s the corrected version of your code:

@@ -23,7 +23,7 @@
       <span class="dialog-footer">
         <el-button @click.prevent="dialogVisible = false"> {{ $t('common.cancel') }} </el-button>
         <el-button type="primary" @click="submit(fieldFormRef)" :loading="loading">
-          {{ isEdit ? $t('common.save') : $t('common.add') }}
+          {{ $t('common.add') }}
         </el-button>
       </span>
     </template>

@@ -34,15 +34,11 @@ import { reactive, ref, watch } from 'vue'
 import type { FormInstance } from 'element-plus'
 import { cloneDeep } from 'lodash'
 import { t } from '@/locales'
-import functionLibApi from '@/api/function-lib'
-import { MsgSuccess } from '@/utils/message'

 const emit = defineEmits(['refresh'])

 const fieldFormRef = ref()
 const loading = ref<boolean>(false)

const form = ref<any>({
  name: ''
})

watch(dialogVisible, (bool) => {
  form.value = {
    name: ''
  }
})

Additionally, I recommend you move the call to open(row) inside the watch listener for dialogVisible. This would ensure that when the modal pops up based on the value of isVisible, the appropriate data is loaded into the form.

Here’s how you can adjust the code:

watch(dialogVisible, (bool) => {
  if (bool && row) {
   	form.value = cloneDeep(row)
  }
  
  form.value = {
    name: ''
	// Remove the line below as it doesn't need to be here
	// isEdit.value = bool // Assuming you want to reflect visibility status here somehow
  }
})

In summary:

1. Remove the reference to isEdit that does not align with its use in the component.
2. Move the logic to load data upon opening the dialog into the watcher for isVisible.
3. Consider whether there should be a different approach to handle edit versus add operations, perhaps using a single method like handleFormSubmit().