Skip to content

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

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

children: [...fields, ...otherFields]
})
return result
}
}
export default {
type: 'form-node',
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The provided code has a couple of issues:

  1. Incorrect Constructor Call: The AppNodeVue import is missing from the constructor call (super()). It should be super(props, FormModel) where FormModel is assumed to be an alternative component that replaces FormNodeVue.

  2. Type Casting Issue: In JavaScript/TypeScript, you cannot directly assign a string property ('label') with another TypeScript object without explicit type casting. You can use parentheses around each assignment inside the map function.

  3. Return Type: The function signature indicates it returns an array but actually assigns results to variables instead before returning them. Consider modifying the logic to accumulate results in memory and then return once after all operations are completed.

Optimization Suggestions:

  • Ensure proper error handling for the field list mapping; consider logging errors or throwing exceptions at appropriate levels.
  • If the form data might change frequently, consider memoizing the derived state to improve performance.
  • Use more descriptive variable names and ensure consistent naming conventions within classes.

@shaohuzhang1 shaohuzhang1 merged commit 8f7d917 into main May 22, 2025
4 of 5 checks passed
@shaohuzhang1 shaohuzhang1 deleted the pr@main@fix_form_node branch May 22, 2025 02:54
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