Skip to content

ReferenceType does not expose valid containedType #2091

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
nbauernfeind opened this issue Jul 17, 2018 · 1 comment
Closed

ReferenceType does not expose valid containedType #2091

nbauernfeind opened this issue Jul 17, 2018 · 1 comment
Milestone
2.12.0

Comments

@nbauernfeind
Copy link
Member

Filing an issue per discussion on the mailing list titled "ReferenceType no bindings."

It feels like it would be useful if ReferenceType's containedType(0) returns the actual reference type. This feels more consistent with how Collection and Map contained types behave.

You'd suggested that you'll look into it perhaps for v2.10 or v3.0.
@cowtowncoder cowtowncoder added 2.11 and removed 2.10 labels Mar 26, 2020
cowtowncoder added a commit that referenced this issue Mar 26, 2020
@cowtowncoder
Minor test improvement wrt #2091
89aebd2
@cowtowncoder
Copy link
Member

Looks like getContentType() returns type, but TypeBindings are indeed empty.
Will postpone until 2.12, likely, since 2.11.0 about to be released.

@cowtowncoder cowtowncoder added 2.12 and removed 2.11 labels Mar 26, 2020
@cowtowncoder cowtowncoder added this to the 2.12.0 milestone May 6, 2020
@cowtowncoder cowtowncoder removed the 2.12 label May 6, 2020
@cowtowncoder cowtowncoder changed the title ReferenceType does not expose valid containedType ReferenceType does not expose valid containedType May 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.12.0
Development

No branches or pull requests
2 participants
@cowtowncoder @nbauernfeind