We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The aim of the open_threads parameter is to enable filtering out those issues whose threads have all been closed, i.e. the issue is resolved.
However, it turns out this means that issues with zero threads (i.e. no discussion yet) are also therefore treated as resolved!
Can I suggest we remove open_threads and replace it with just is_open/open_issues/open_only or whatever?
open_threads
is_open
open_issues
open_only
There is no backwards compatibility as the only API user of this is code under my control that I can easily change.
The text was updated successfully, but these errors were encountered:
I'm using an inner join so zero threads do not count as open. I'm not checking if the thread is public though...
Sorry, something went wrong.
3db5a20
Could you revert this specific change - it has suddenly vastly reduced the number of issues.
We'll look at a better fix shortly.
42ea032
Great, thanks.
No branches or pull requests
The aim of the open_threads parameter is to enable filtering out those issues whose threads have all been closed, i.e. the issue is resolved.
However, it turns out this means that issues with zero threads (i.e. no discussion yet) are also therefore treated as resolved!
Can I suggest we remove
open_threads
and replace it with justis_open
/open_issues
/open_only
or whatever?There is no backwards compatibility as the only API user of this is code under my control that I can easily change.
The text was updated successfully, but these errors were encountered: