Fix project search membership filter type - #525
Merged
Conversation
iurisilvio
approved these changes
Sep 3, 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
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.
Description
The Python SDK typed
in_datasetas a project name even though project image search treats it as a boolean membership filter, so this alignsProject.search()andProject.search_all()with the API contract without changing request behavior. The package version is bumped to1.4.3; companion documentation is in roboflow/docs#228.Type of change
How has this change been tested?
python -m unittest tests.test_projectruff check roboflow/core/project.pyruff format --check roboflow/core/project.pyAny specific deployment considerations