Allow setting the complexity value (cost) of a field to 0

[sgabler]

We will use the operation complexity (cost) as a measure for calculating the usage of a user per month, which we will then bill.

Some fields we offer in our schema are just wrappers that don't really cost us anything to calculate, and thus should not be billable.

Example:

query EXAMPLE {
  sites(first:10) {
    nodes {
      name
      data {
        acInverterYield {
          daily {
            dataPoints {
              value
              timestamp
            }
          }
        }
      }
    }
  }
}

In this example, the fields data and acInverterYield are just wrappers. The actual calculation will happen once the user selects the granularity, e.g. daily or monthly.

So in the above example we would like to set the complexity of the fields data and acInverterYield to 0 by using .Cost(0), but this is not possible due to the error: "The complexity cannot be below one."

Would it be possible to allow setting the complexity to 0 in the future, or do you think that this is a wrong approach here? Curious to hear some opinions 🙂

[michaelstaib]

This is now implemented