Skip to content
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

Violin attributes/values missing from plot-schema.json #4617

Closed
hmf opened this issue Mar 6, 2020 · 4 comments
Closed

Violin attributes/values missing from plot-schema.json #4617

hmf opened this issue Mar 6, 2020 · 4 comments

Comments

@hmf
Copy link

hmf commented Mar 6, 2020

Posted a related question in here but I think it may be an error because I found another issue. Hence this report here. Describing two missing elements.

Background: I am using the schema to auto-generate Scala code to read and generate the Plotly JSON documents. I have started with the Violin trace examples for preliminary tests. I have found that:

  • The attribute: points: 'none' does not exist in the schema. The schema points is an enumerated that only has the following values:
    • “all”
    • “outliers”
    • “suspectedoutliers”
    • false
  • The element "boxpoints": false does not appear in the Violin trace. The only place I find this is in the box trace.

So am I correct in assuming that these are missing from the schema? Can I use this schema to generate the intended code?

@nicolaskruchten
Copy link
Contributor

You can use the schema to generate code, this is what we do in Plotly.py. It's normal that boxpoints isn't available in violin and I don't believe that 'none' is an accepted value for violin.points, indeed.

I suspect the documentation is wrong rather than the schema ;)

@hmf
Copy link
Author

hmf commented Mar 6, 2020

Ok, I will assume these are schema errors then. Thanks.

@hmf hmf closed this as completed Mar 6, 2020
@nicolaskruchten
Copy link
Contributor

(You mean documentation errors, right? The schema is automatically derived from the internal data structures used by Plotly.js, so it's very unlikely that the schema is wrong :)

@hmf
Copy link
Author

hmf commented Mar 9, 2020

Oops. I confess I am Plotly illiterate. Ok then I have opened a new issue for a a documentation error. Thanks for the explanation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants