-
Notifications
You must be signed in to change notification settings - Fork 2
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
Operator input/output label reactive #6581
Conversation
…utput-panels-of-create-model-from-equations-edit-model-and-stratify-model-fully-editable
…utput-panels-of-create-model-from-equations-edit-model-and-stratify-model-fully-editable
…utput-panels-of-create-model-from-equations-edit-model-and-stratify-model-fully-editable
…s-of-create-model-from-equations-edit-model-and-stratify-model-fully-editable' into operator-input/output-label-reactive
// default use single output type | ||
return useProjects().getAssetName(selectedOutput.value?.[0]) || selectedOutput.label; | ||
const label = useProjects().getAssetName(assetId).value; | ||
return computed(() => (!isEmpty(label) ? label : (selectedOutput.label ?? ''))); |
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.
There seems to be a couple of extra layers of unnecessary computed going. on here, what is the problem here? The PR description is blank so I am not even sure what to test for ??
The goal was to solve the issue that input/output are not reactive to change. Maybe this old PR is not worth reopening anymore. |
No description provided.