-
Notifications
You must be signed in to change notification settings - Fork 2.2k
fix: Edit advanced orchestration applications, add application nodes, and display that some applications are unavailable after being added #2945
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
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The provided code appears to be a functional component for updating field properties within a workflow node data structure. The key operations involve merging
new_api_input_field_list
andold_api_input_field_list
, handling missing fields, and similarly foruser_input_field_list
. Here are some review points to consider:Regularity Checks
err
) which means the exact nature of errors might not be fully captured.Potential Issues
Empty Lists: If either
new_api_input_field_list
orold_api_input_field_list
is empty, attempting to map over them without checking for emptiness can lead to undefined behavior.Label Assignment: Ensure that the assignment logic for labels handles both object values and primitive types correctly.
Status Update: While using
set(props.nodeModel.properties, 'status', 500)
when there's an error is useful, it would generally be more informative to include specific error messages in logs or UI updates.Optimization Suggestions
Avoid Nullish Coalescing Twice:
You can optimize this by removing one level of nesting.
Use Immutability Libraries:
Consider using libraries like Ramda for utility functions that help with immutability better than plain JavaScript methods.
Example usage with Ramda:
Code Readability: Break down complex conditional checks into separate helper functions or inline conditions where necessary.
Consistent Logic Across Fields:
Ensure consistent naming and approach for finding fields across different input lists to avoid redundancy and complexity.
Conclusion
The provided code is mostly functional, with minor improvements suggested for code readability and efficiency. Addressing these points will enhance maintainability and performance.