kt3k on gh-pages
Deploy c3js/c3 to github.com/c3… (compare)
kt3k on master
Typo fix (#2568) (compare)
Hello everyone, I have a bit of a theoretical question on c3. When generating a chart, is it correct to say that you pass the generate method a configuration object as an argument? Say I would like to use some pure d3 on the chart I just generated, how would I be able to, for example, log the actual chart object that was generated to see what I can alter?
Just to recap (please, do tell me if I'm wrong): the way I see it is when we use c3 generate we create a d3 object with a lot of default sorted out. What I am looking for is a way to inspect the actual d3 object that was generated to make changes to it using d3.
expect(true).toBeTruthy();DOES NOT A UNIT TEST MAKE. :weary:
If you run grep "expect(true).toBeTruthy()" spec/* | wc -l, you get 140. That means of the ~400 assertions made across all unit tests, 140 mean absolutely nothing.
140 of our unit tests test absolutely nothing