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

Template: options seem not to work (and/or missing documentation) #3032

Closed
fsmeier opened this issue Sep 20, 2018 · 3 comments
Closed

Template: options seem not to work (and/or missing documentation) #3032

fsmeier opened this issue Sep 20, 2018 · 3 comments

Comments

@fsmeier
Copy link

fsmeier commented Sep 20, 2018

Bug or missbehaviour or missing documentation:

When working with the new template property which got introduced with #2761 it looks like some options are not working.

So far I could identify to options which are not working in the template:

{
  layout: {
    xaxis: {
      range: [0, 10],
      autotick: false
    }
  }
}

But when I put them directly into the layout without template they work as expected:

Not working: https://codepen.io/anon/pen/VGgBRr
Working: https://codepen.io/anon/pen/qMgywj

At least those both are not working, maybe even more.

For the templates there is no documentation at all (or I am blind) except of the snipped i found here: https://github.com/plotly/plotly.js/pull/2761/files#diff-e08811dc2d34fabaf8eee6ba73afaa01R198
But i can not find a description in https://plot.ly/javascript/reference

Related to: #2469
Maybe @alexcjohnson can tell more

Hope I did not forget anything,
all the best from Berlin

@etpinard etpinard mentioned this issue Sep 27, 2018
3 tasks
@etpinard
Copy link
Contributor

Here's a working version: https://codepen.io/etpinard/pen/ReVgXB?editors=1010

The problem here is: axis.autotick is a deprecated attribute (try calling Plotly.validate([], {xaxis: {autotick: false}})) which template don't support.

Someone could argue that deprecated attributes should be allowed in templates, but I'd vote 👎 here.

@etpinard
Copy link
Contributor

Closing.

If someone puts forward an argument for accepting deprecated attributes in templates, we'll open another issue about then.

@fsmeier
Copy link
Author

fsmeier commented Oct 12, 2018

@etpinard Yes, should not be there if it is deprecated anyway!
Is there an issue for marking it deprecated in the docu yet? Have not seen this notice in the reference yet.

Also: what about range, also deprecated?

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