tree 431b2790b470b78803dc45b27e84563e33930b63
parent d5041a1df187609d00a1ba846d06a586eaa1f503
author Paul Jolly <paul@myitcv.org.uk> 1621339049 +0100
committer Paul Jolly <paul@myitcv.org.uk> 1621342251 +0000

encoding/openapi: finalise when constructing openapi AST

When building OpenAPI enums from a CUE instance, specifically one that
contains an enum imported from protobuf, we don't care about the
definition-encoded integer enum value (introduced as part of dcfff000).
Instead we only care about the final value of the enum.

Prior to dcfff000, an imported protobuf enum would look like this:

    #CaptureMode: "DEFAULT" | "IPTABLES" | "NONE"

Post dcfff000, it looks like:

    #CaptureMode: {
            "DEFAULT"
            #enumValue: 0
    } | {
            "IPTABLES"
            #enumValue: 1
    } | {
            "NONE"
            #enumValue: 2
    }

Therefore, in the process of building an enum we simply need to finalise
the CUE Value prior to deriving its syntax.

The test as part of this CL comes from a real Istio schema that
uncovered this bug in the first place.

Fixes #977

Change-Id: I5b4cbb2f35b0535488d8f77b1e2166f89ed2644d
Reviewed-on: https://cue-review.googlesource.com/c/cue/+/9843
Reviewed-by: CUE cueckoo <cueckoo@gmail.com>
Reviewed-by: Marcel van Lohuizen <mpvl@golang.org>