The golang docsonnet loader expects booleans to have a type string of boolean whereas the doc-util library injects type strings of bool. This causes all rendering for booleans to fail unless you eschew usage of d.T.boolean and manually pass 'boolean' when declaring a d.val.
Lots of libraries are already annotated with docsonnet using d.T.boolean but who knows how many people are using the workaround of explicitly passing 'boolean' to the value constructor. In order to break as few people as possible, we should modify https://github.com/jsonnet-libs/docsonnet/blob/master/doc-util/main.libsonnet#L223 so that it evaluates to 'boolean'.
The golang docsonnet loader expects booleans to have a type string of
booleanwhereas the doc-util library injects type strings ofbool. This causes all rendering for booleans to fail unless you eschew usage ofd.T.booleanand manually pass'boolean'when declaring ad.val.Lots of libraries are already annotated with docsonnet using
d.T.booleanbut who knows how many people are using the workaround of explicitly passing'boolean'to the value constructor. In order to break as few people as possible, we should modify https://github.com/jsonnet-libs/docsonnet/blob/master/doc-util/main.libsonnet#L223 so that it evaluates to'boolean'.