Apollo Client has grown a lot over the past few years, and we’ve managed to do some really incredible things with a very small team. Unfortunately, one pretty important thing we have not done a great job with, is staying on top of our GH issue backlog . We’re constantly building new features and squashing bugs, but our response times on some issues can be very slow, and we’re actively working to change this. We value all of the issues the Apollo community has opened in the AC repo, and more importantly we value the time people have taken our of their lives to report problems with AC.
The above being said, before we can start to improve our issue triaging response times, we need to get our large issue backlog under control. Most of the open issues in the AC repo have actually been fixed, but the issues themselves have not been updated to reflect that. To help with this, we’re doing large rounds of spring issue cleaning, and are hoping to have the outstanding issue backlog under control in a few weeks. To do this however, we have to make certain assumptions about some of the open issues, and are closing them if they seem like they could be fixed. There aren’t enough hours in the day for Apollo staff to dig into the hundreds of open issues, so we’re relying on community members to let us know if we close an issue that they think is still valid. We’re sorry in advance for any frustration this might cause, and please know that we’re not doing this because we don’t care - quite the opposite - we care massively about your input, and are striving to get our issue triaging on a better footing, and ultimately help make sure the problems you encounter are resolved in a more timely fashion.
If you have any issues with this approach, definitely let us know!