-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
Member of a @define
d elements is also generated
#127
Comments
Added related tests but, weird, I was not actually able to reproduce. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A member of a
@define
d element is also generated (as if not using the annotation), but it should not.To Reproduce
Use this input config schema:
This will generate:
Java:
Scala:
Expected behavior
As documented, the
@define
annotation by itself should only generate the corresponding type (a class in the above example) in the target language.Target language(s):
Additional context
Although not really surprising (due to the WiP status for a full shared object definition support), this was really exposed while looking into #125 .
EDIT: Actually, this used to work as intended AFAICR so this looks like a regression.
The text was updated successfully, but these errors were encountered: