In order to perform refactoring and to add new features with more confidence, we need unit, integration and end-to-end tests for:

• algorithm parts. Seesrc/algorithms

• React parts - components and pages. See src/components and src/pages

• State management: redux reducers and sagas. See src/state

The infrastructure:

• jest and @testing-libraryare already set up. Un

Great stuff! I'm planning to use API for my dashboard Pandemic Estimator but I wish your API had a better documentation on methodology. I'm using JHU directly and I know what chaos it is, the most blatant example being that they provide "cumulative data" that's not cumulative quite often in practice. And the whole change of file formats, etc.

Can you please de

Pain point :
Many of our the analysts are not familiar with using the API for analysis.

Solution:
A google script can easily fetch the data from the API and store it in their personal Google Sheet every 30 minutes or so.
If we can create the script and write a simple document on how to do this, it would be a great help!

Following the tutorial here and just need to add installation of the libraries at the top of the notebook

https://colab.research.google.com/github/googlecolab/colabtools/blob/master/notebooks/colab-github-demo.ipynb#scrollTo=8QAWNjizy_3O

Starting a thread for some related ideas that have been sitting on my to-do list.

I think we should provide some help in interpreting the graph. Like a how to read this graph section. (Currently we point folks to the related Minute Physics video, but we can't assume folks have watched this.) This could be some kind of overlay that is shown the first time a user visits the page, which explains

Can be done by changing layout.geo.lataxis.range and layout.geo.lonaxis.range as described in https://plot.ly/python/map-configuration/#map-projections (scroll down a bit).

The corresponding part of the code is https://github.com/covid19-dash/covid-dashboard/blob/master/make_figures.py#L49 (you can also call directly fig.update_geos).

Since this is a repo themed around openness, I suggest to go for CC0 (for text, media and any associated code or data).

We should add some pagination to all organization CRUD lists. We can limit items to 30 for now.

I'm at PyBeachLA right now about to run sprints, and I think I can get some sprinters here involved. Docs are usually a good starting point for people who aren't ready to jump into code yet.

I'm thinking a docs/ folder with Markdown files, connected via webhook to ReadTheDocs.org?

Or do you have other suggestions/ideas?