-
Notifications
You must be signed in to change notification settings - Fork 54
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
Inheritance and Member type precedence not working #366
Comments
Hi @pksunkara, is that a bug or did I miss something? |
@jmatsushita Thanks for the report. This is definitely a bug. |
Hi @pksunkara, have you been able to reproduce and maybe look into this? |
@jmatsushita Yes, we've confirmed this bug. It's on our agenda to fix and it's one of the next up bugs which we will hopefully tackle in the next two weeks. When we're expanding and rendering the JSON Schema for an MSON property in Drafter, we're not taking into account some of the overridden attributes (description, type, etc) which we will need to fix. Thanks for reporting. |
I've seen a number of inheritance fixing pull requests and issues, but I'm not sure if I understand whether the MSON spec is supposed to be implemented in that regard.
In particular the member type precedence doesn't seem to work for me with
protagonist@1.4.1
which if I understand correctly includesdrafter@3.0.0
.Using the same example as in the spec (augmented with some descriptions):
Piped through
refract.py
gives:According to the doc,
last_name
shouldn't be required no? In addition shouldn't the description oflast_name
be"Last name"
?The text was updated successfully, but these errors were encountered: