Adding fieldConfig overrides in table panel

[vishnuchalla]

Description

Adding filterable option in table panel. More context here: https://github.com/grafana/grafonnet/issues/126

Testing

Tested by building a grafana panel. Could see expected json and filter option in the table panel.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Vishnu Challa seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[vishnuchalla]

@K-Phoen @iainlane Requesting a review.

[Duologic]

It exists in the schema, I've been looking through docs for relevance of this field, we can enable it here instead: https://github.com/grafana/grafonnet/blob/main/generator/core.libsonnet#L271

[Duologic]

Fixing this in #131

[vishnuchalla]

@Duologic

Fixing this in #131

I still do not understand the usage of it. It tried both

• table.fieldConfig.defaults.withFilterable

  RUNTIME ERROR: field does not exist: fieldConfig

• table.standardOptions.withFilterable

  RUNTIME ERROR: field does not exist: withFilterable

I think the field is not properly exposed yet for table panel atleast.

[Duologic]

Did you do a jb update?

[vishnuchalla]

I did update and retry this. when I do a table.fieldConfig.defaults.withFilterable, I still see this error

RUNTIME ERROR: field does not exist: fieldConfig

And when I do table.standardOptions.withFilterable, the filter seems to be getting applied but in a wrong place i.e fieldConfig.defaults.filterable instead of fieldConfig.defaults.custom.filterable. So I am unable to see filter options in my dashboard.

[Duologic]

Gotcha, so there is a distinct field fieldConfig.defaults.custom.filterable that is not in the table schema. Makes sense to investigate that deeper, I find a reference here which shows that there are more fields missing. Let's see how we can get those into Grafonnet too.

[Duologic]

134 makes an attempt to fix this again.

[Duologic]

134 got merged