Custom Datasource API - Precendence of Aggregations in fields response

Hello,
 
On version 2.8.33, with the response for the /field request, we noticed that if the array of aggregations was empty for a particular field, the array of aggregations at the top level did not take precedence. For example, on version 2.8.33, the following response for the /field request:

{
  aggregations: {
    number: ["sum"]
  },
  fields: [
    {
      uniqueName: "Test",
      aggregations: []
    }
  ]
}

would result in "Test" having no aggregation options in the fields popup. However, in version 2.9.3, the response does result in "Test" having the sum option in the fields popup.
 
Our intent with the empty aggregations array was to prevent a particular field from being aggregated and form being placed in the "Values" section in the fields popup. For example, we wanted to restrict "Test" to only being placed into "Report Filters," "Columns," or "Rows," but not "Values" since we wanted "Test" to act more as a "dimension" than a "cell" value.
 
Is there a way to turn off all aggregations for a particular field despite having a non-empty aggregations array at the root level?
 
Kind regards,
Henry