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

Upgrade to Chart.js 3.x #12

Closed
wants to merge 1 commit into from
Closed

Conversation

benmccann
Copy link
Collaborator

@benmccann benmccann commented Mar 13, 2020

We probably don't want to merge this yet, but I'm just sharing what will need to happen to make the tests work for 3.x

I'm not sure why I had to change t to x. Looking at the docs, it doesn't seem like I should have to do that.

@Imperatorn
Copy link

We probably don't want to merge this yet, but I'm just sharing what will need to happen to make the tests work for 3.x

I'm not sure why I had to change t to x. Looking at the docs, it doesn't seem like I should have to do that.

Hint from the Migration guide:

"TimeScale does not read t from object data by default anymore. The default property is x or y, depending on the orientation. See data structures for details on how to change the default."

@woodhull
Copy link

Does this mean the adapter does not currently work properly with chart.js 3?

@kurkle
Copy link
Member

kurkle commented Aug 31, 2020

Does this mean the adapter does not currently work properly with chart.js 3?

No, only the tests are not working with v3 before this gets merged.

@sakulstra
Copy link

sakulstra commented Sep 1, 2020

@kurkle No, only the tests are not working with v3 before this gets merged.

I just tried testing chart-js 3 beta, for me this fails within this chartjs-adapter-luxon package due to: 'chart.js' does not contain a default export (imported as 'Chart')

As I get it there's no default export any more, https://github.com/chartjs/chartjs-adapter-luxon/blob/master/src/index.js#L1 fails atm. Also _adapters seem to be no longer exposed 🤔

Am I doing sth wrong or is this statement lo longer true with alpha-2 and beta? The first alpha seems to still work.

@etimberg
Copy link
Member

etimberg commented Mar 7, 2021

Resolved in #29

@etimberg etimberg closed this Mar 7, 2021
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

Successfully merging this pull request may close these issues.

6 participants