Closed sweisss closed 3 weeks ago
Since this will most likely involve another database migration, consider rolling in the removal of the default emoji to the migration, since the default emoji doesn't appear to be necessary.
Forgot to tag this in PR #45
Since the last database migration, there is no longer any onConflict strategy for ForecastLink names, and because the primary key is now an autogenerated id (Int), when the Add Defaults setting is selected, duplicates are added.