Skip to content

[FL-729] [FLPY-7] Dimensioned Volume Output #1012

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 7 commits into from
Jun 9, 2025

Conversation

benflexcompute
Copy link
Collaborator

Previous implementation: #992

if isinstance(field, str):
udf_expression = generate_predefined_udf(field, input_params)
if udf_expression:
generated_udfs.append(UserDefinedField(name=field, expression=udf_expression))
Copy link
Contributor

Choose a reason for hiding this comment

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

This UserDefinedField type looks very similar to what a UserVariable is - do you think we could leverage this or is there some extra business logic that we need to take care of? Maybe we could inherit?

@benflexcompute benflexcompute changed the title [FL-729] [FLPY-7] Dimensioned Output [FL-729] [FLPY-7] Dimensioned Volume Output Jun 5, 2025
@benflexcompute benflexcompute force-pushed the BenY/FL-729-DimensionedOutput branch from 3a7a3ac to 7989040 Compare June 9, 2025 13:18
@benflexcompute benflexcompute merged commit 4a1db3e into expressions Jun 9, 2025
15 checks passed
@benflexcompute benflexcompute deleted the BenY/FL-729-DimensionedOutput branch June 9, 2025 20:48
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.

2 participants