Error in filter list when using null

When using NULL in _list conditions in applyFilter, an error is thrown.

"An exception occurred while executing 'SELECT o0_.id AS id_0, o0_.abundance AS abundance_1, o0_.out_of_method AS out_of_method_2, o0_.comment AS comment_3, o0_.sex AS sex_4, o0_.is_dead AS is_dead_5, o0_.species AS species_6, o0_.row_id AS row_id_7, o0_.created_at AS created_at_8, o0_.modified_at AS modified_at_9, o0_.developmental_stage_id AS developmental_stage_id_10, o0_.section_event_id AS section_event_id_11, o0_.created_by_id AS created_by_id_12, o0_.last_modified_by_id AS last_modified_by_id_13 FROM \"observation\" o0_ LEFT JOIN \"section_event\" s1_ ON o0_.section_event_id = s1_.id LEFT JOIN \"section\" s2_ ON s1_.section_id = s2_.id LEFT JOIN \"transect\" t3_ ON s2_.transect_id = t3_.id LEFT JOIN \"view_observation_aggregates\" v4_ ON o0_.id = v4_.observation_id WHERE v4_.qs_status IN (?, ?) AND o0_.id >= ?' with params [\"null\", \"-1\", \"4\"]:\n\nSQLSTATE[22P02]: Invalid text representation: 7 ERROR:  invalid input syntax for integer: \"null\""

AC

• FilterHitory that contains conditions like this can be used in applyFilter mutation:

  {"aggregate_qsStatus_is_list":["null","-1"]}
  {"aggregate_qsStatus_is_list":["null","-1"], "id_gte": "4"}

• Tests (api-base)

Review

• FilterHitory that contains conditions like this can be used in applyFilter mutation:

  {"aggregate_qsStatus_is_list":["null","-1"]}
  {"aggregate_qsStatus_is_list":["null","-1"], "id_gte": "4"}

• Tests (api-base)