Open
Conversation
rishiy15
approved these changes
Apr 2, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Item id is 26-character lowercase alphanumeric shape but this can be the came for some item titles.
get_itempreviously treated every such string as an id, so lookups by title could fail even though the API could resolve the item via the title filter.This change tries
get_item_by_idfirst when the string matches that shape, and on HTTP 404 falls back toget_item_by_titlewith the same string. Other errors (for example 401) are unchanged and are not treated as a title lookup.Resolves: #80
Testing