Looks nice, 0 dependency, simple design but there is one issue... I see that you don't have a single unit test or integration or functional etc. Even if your in house developers know what they are doing (which is a myth, stuff will break) it's going to be difficult accept contributions from community without any tests that make (almost) sure existing features are working with the changes.
Show HN: Frappe Charts – GitHub inspired JavaScript charting with zero dependencies
51–60 of 92 posts
Re: Show HN: Frappe Charts – GitHub inspired JavaScript charting with zero dependencies
#52Earlier quoted context omitted.
I see where your coming from, but I disagree. This isn't a new OS, its a tiny charts library/utility. I'm more inclined to contribute because there are no tests. Either way, someone could PR tests if they wished. Perhaps your comment should have been such a PR? ;)
Why would lack of tests be a measure for your desire to contribute?
Re: Show HN: Frappe Charts – GitHub inspired JavaScript charting with zero dependencies
#53Re: Show HN: Frappe Charts – GitHub inspired JavaScript charting with zero dependencies
#54Looks nice, 0 dependency, simple design but there is one issue... I see that you don't have a single unit test or integration or functional etc. Even if your in house developers know what they are doing (which is a myth, stuff will break) it's going to be difficult accept contributions from community without any tests that make (almost) sure existing features are working with the changes.
Some of us believe that tests increase work by 25% while only reducing defects by 60%. https://www.microsoft.com/en-us/research/wp-content/uploads/...
TIL
Re: Show HN: Frappe Charts – GitHub inspired JavaScript charting with zero dependencies
#55Earlier quoted context omitted.
I am glad that this approach works for you but I am not brave enough to use a new library without a single test.
I guess this project isn't for you then.
Re: Show HN: Frappe Charts – GitHub inspired JavaScript charting with zero dependencies
#56Earlier quoted context omitted.
Judge work by what it does, not by what it doesn't have. Like users, programmers don't care whether programs have tests as long as it does what it needs to do.
Tests are a way to judge what it does. It does the judging for you, ensuring features work as advertised, and provide usage examples that are guaranteed to work.
Re: Show HN: Frappe Charts – GitHub inspired JavaScript charting with zero dependencies
#57Earlier quoted context omitted.
So I should wait until stuff starts breaking, then start complaining.
If nothing breaks why would you complain?
Re: Show HN: Frappe Charts – GitHub inspired JavaScript charting with zero dependencies
#58Earlier quoted context omitted.
I see where your coming from, but I disagree. This isn't a new OS, its a tiny charts library/utility. I'm more inclined to contribute because there are no tests. Either way, someone could PR tests if they wished. Perhaps your comment should have been such a PR? ;)
Why would lack of tests be a measure for your desire to contribute?
Re: Show HN: Frappe Charts – GitHub inspired JavaScript charting with zero dependencies
#59Also, for the clickable charts, clicking on the popover should count as well. If the bar is really short it can be quite hard to click on, such as the 2007 entry in the first chart.
Re: Show HN: Frappe Charts – GitHub inspired JavaScript charting with zero dependencies
#60Question: For codebases that are all about package managers Yarn, what's best practice for integrating something like this? Just push it into a 'vendor' folder?
If you're using something like Webpack and the library just places everything on the global scope, you can configure exports-loader [0]. That way you can reference the module as if it were written with CJS or ESM, without having to change the source.
If it's not published on npm, you can reference the git repo along with the specific release tag you want to use. My suggestion would be to fork the repo and point to your fork in package.json, so things continue to work if the original repo ever gets taken down.