Allow users to search issues without retrieving fields #1933
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
for more information, see https://pre-commit.ci
beliaev-maksim
had a problem deploying
to
check
GitHub Actions
Failure
Contributor
Author
|
let me know if you are interested in PR, then I can rebase it |
studioj
reviewed
Apr 1, 2025
| validate_query (bool): True to validate the query. (Default: ``True``) | ||
| fields (Optional[Union[str, List[str]]]): comma-separated string or list of issue fields to include in the results. | ||
| Default is to include all fields. | ||
| Default is to include all fields. If you don't require fields, set it to empty string ``''``. |
Collaborator
There was a problem hiding this comment.
search issues has been deprecated and slightly reworked
i'd suggest implementing it at enhanced_search_issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR allows users to perform a search without specifying fields. While this is already possible with the current implementation, the service still makes an unnecessary API call to cache fields. This PR resolves that issue by validating the fields cache only when the user explicitly requests fields.