Skip to content

fix: The dropdown data of subsequent nodes in the form cannot be displayed back #3131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 22, 2025

Conversation

shaohuzhang1
Copy link
Contributor

fix: The dropdown data of subsequent nodes in the form cannot be displayed back

Copy link

f2c-ci-robot bot commented May 22, 2025

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.

Copy link

f2c-ci-robot bot commented May 22, 2025

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

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

@shaohuzhang1 shaohuzhang1 merged commit 9d7a383 into main May 22, 2025
4 checks passed
@shaohuzhang1 shaohuzhang1 deleted the pr@main@fix_form_node branch May 22, 2025 06:36
} catch (e) {}
result.push({
value: this.props.model.id,
label: this.props.model.properties.stepName,
type: this.props.model.type,
children: [...fields, ...otherFields]
children: fields
})
return result
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here is a review of the provided code:

Issues:

  1. Redundancy: The otherFields array is created but not used within the scope where it's defined, leading to potential memory wastage.
  2. Simplification: Instead of mapping over form_field_list, you can use an arrow function directly. This reduces unnecessary steps.
  3. Type Checking: The code assumes that all properties have a non-null .properties object with nested objects. Ensure this assumption holds true.

Optimizations:

  1. Remove Unnecessary Variable Assignment: Since fields will be populated based on form_field_list, there’s no need to create otherFields.

Here's the revised code:

class FormNode extends AppNode {
  get_node_field_list() {
    const result = [];
    
    try {
      this.props.model.properties.node_data &&
      this.props.model.properties.node_data.form_field_list.length > 0 &&
      
      this.props.model.properties.node_data.form_field_list.forEach((item: any) => {
        // Check if the field already exists in fields
        if (!fields.includes(item.field)) {
          fields.push({
            value: item.field,
            label: typeof item.label == 'string' ? item.label : item.label.label
          });
        }
      });
      
    } catch (e) {}

    result.push({
      value: this.props.model.id,
      label: this.props.model.properties.stepName,
      type: this.props.model.type,
      children: fields || []
    });

    return result;
  }
}

This refactored version of your method should perform better and reduce memory usage without any functionality changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant