Repository navigation
fix: handle Actors without a description in ApifyActorsTool - #50
Merged
Merged
Conversation
vdusek
approved these changes
Nov 3, 2026
vdusek
left a comment
vdusek
left a comment
There was a problem hiding this comment.
A few nits like comments/docstrings clarity, and test case ids; otherwise LGTM 🚀.
protoss70
approved these changes
Nov 5, 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.
ApifyActorsToolcrashed with aTypeErroron Actors without adescriptioninactor.json(e.g.apify/web-scraper,apify/google-trends-scraper), because since apify-client 3.4.0 the build dump returns it asNoneinstead of leaving it out. BothactorDefinitionreads now treatNonelike a missing key, anduv.lockmoves to apify-client 3.4.0 so the tests run against what users install.Part of apify/dx-heroes-team#31.