good_issues.md

Generally, to make it easier to diagnose the issues:

1. Debug each part of your code yourself, eliminating potential bug sources beyond the bounds of this library. I.e, verify your back end fetching and parsing code results in valid data, then use that in your issue.
2. Simplify the code as much as possible, removing styling, unrelated logic etc (this may help you identify the issue as well).
3. Add full errors and stack traces.
4. Use <details> tags liberally so the main issues are front loaded, but context isn't lost.
5. Use code formatting blocks:

   ```dart
   /// your cleaned up, commented code
   ```

This will help distill exactly where the problematic code is, both for yourself and others.