Skip to content

Conversation

@jasonbahl
Copy link
Collaborator

What does this implement/fix? Explain your changes.

This ensures that the $settings_fields param passed to the graphql_get_setting_section_field_value filter is an array as documented in the filter params. Previously the value was documented to be an array, but was not always returning an array.

Does this close any currently open issues?

closes #3138

…ion_field_value" filter is an array before passing it to the filter
@jasonbahl jasonbahl requested a review from josephfusco May 21, 2024 18:56
@jasonbahl jasonbahl self-assigned this May 21, 2024
@qlty-cloud-legacy
Copy link

Code Climate has analyzed commit 9a80f69 and detected 0 issues on this pull request.

View more on Code Climate.

@jasonbahl jasonbahl changed the title fix: $settings_fields param on "graphql_get_setting_section_field_value" filter not passing the correct type May 21, 2024
@coveralls
Copy link

Coverage Status

coverage: 84.37%. remained the same
when pulling 9a80f69 on fix/3138-graphql_get_setting_section_field_value-param-type
into 5d3cd82 on develop.

Copy link
Member

@josephfusco josephfusco left a comment

Choose a reason for hiding this comment

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

Looks good! Possibly add tests to cover this scenario from popping up again

@jasonbahl jasonbahl merged commit 5a0f707 into develop May 30, 2024
@jasonbahl jasonbahl mentioned this pull request Jun 5, 2024
@justlevine justlevine deleted the fix/3138-graphql_get_setting_section_field_value-param-type branch December 28, 2024 22:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: graphql_get_setting_section_field_value filter params return different types than documented

4 participants