pass_row parameter should be an input to the field_update step to support functions #1728
Comments
ebAbhay
added a commit
to Engine-B/frictionless-py
that referenced
this issue
Jan 22, 2025
…ld_update # Description As described in frictionlessdata#1728, pass_row parameter is now added as an editable parameter for the field_update step. This allows us to use row data inside custom python function. # Tests Ensured the newly added unit test ` test_step_field_update_with_function_and_pass_row_true` runs without fail and also that all the previous test cases run and pass too.
pierrecamilleri
added a commit
that referenced
this issue
Jan 27, 2025
# Description As described in #1728, pass_row parameter is now added as an editable parameter for the field_update step. This allows us to use row data inside custom python function. The default value of the parameter remains False so that any existing uses of this functionality will not be affected. # Tests Ensured the newly added unit test `test_step_field_update_with_function_and_pass_row_true` runs without fail and also that all the previous test cases run and pass too. - fixes #1728 --------- Co-authored-by: Pierre Camilleri <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
In the
field_updatestep, thepass_rowparameter is set toFalseby default, except forformulawhich sets it toTruebefore calling thetable.convert()from petl. We should allow this parameter to be set toTrueforfunctionsas well for the same reasons thatformulasets it toTrue.The text was updated successfully, but these errors were encountered: