Error on recursive types

[DirectXMan12]

Right now, we can't support recursive types, because those require references, and SIG API Machinery has thus far been reluctant to add reference support to CRDs (intra-object references would do the trick, and they seem slightly more amenable to those, so someone might be able to champion that in the long term).

We should warn/error on recursive types, to avoid the confusing behavior today where we just don't generate type info for them.

Spawned from #477.

/kind bug
/help
/priority important-longterm

[k8s-ci-robot]

@DirectXMan12:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

Right now, we can't support recursive types, because those require references, and SIG API Machinery has thus far been reluctant to add reference support to CRDs (intra-object references would do the trick, and they seem slightly more amenable to those, so someone might be able to champion that in the long term).

We should warn/error on recursive types, to avoid the confusing behavior today where we just don't generate type info for them.

Spawned from #477.

/kind bug
/help
/priority important-longterm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[cscetbon]

@DirectXMan12 I'm hitting this issue with the following type

type Throwable struct {
	Cause            *Throwable   `json:"cause,omitempty"`
	Stacktrace       []StackTrace `json:"stackTrace,omitempty"`
	Message          string       `json:"message,omitempty"`
	LocalizedMessage string       `json:"localizedMessage,omitempty"`
	Suppressed       []Throwable  `json:"suppressed,omitempty"`
}

Is there a workaround ?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.