Joshua Verdin

__Expected behavior:__
A clear and concise description of what you expected to happen.

__Describe the bug:__
A clear and concise description of what happened instead of the expected behavior.

__Reproduction:__

Add a failing test to the suite and submit a PR. A test is even better than a fix.
Alternatively create a [codesandbox.io](https://codesandbox.io/) with the issue. Make it as minimal as possible as this will help us find the bug quicker.

__Versions (please complete the following information):__
- jss:
- Browser [e.g. chrome, safari]:
- OS [e.g. Windows, macOS]:
Feel free to add any additional versions which you may think are relevant to the bug.

__Managing expectations:__

Maintainers will not be fixing the problem you have unless they have it too, if you want it to get fixed:

1. Submit a PR with a failing test
2. Discuss a solution
3. Implement it

You can also do the first step only and wait for someone else to work on a fix. Anything is much better than nothing.

No concrete bug, reproduction, version information, file, test, or entry point is provided. Start by requesting the missing expected behavior, actual behavior, reproduction, and environment details; done cannot be defined until a minimal failing test or CodeSandbox is supplied.

Written by the indexing model from the issue text.