Feature/remove get available tags#467
Closed
Shashankss1205 wants to merge 2 commits into
Closed
Conversation
f08cd15 to
ea4fe5b
Compare
ea4fe5b to
7704998
Compare
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.
Reference Issues/PRs
See also:
feature/data_managementWhat does this implement/fix? Explain your changes.
This PR cleans up legacy, unused docstring comments referencing the
get_available_tagstool inlist_estimators.py.The
get_available_tagstool was previously unified and integrated into thequery_registrytool undertarget="tags". Removing these legacy docstrings prevents developer and LLM confusion when interacting with the discovery tool catalog.Does your contribution introduce a new dependency? If yes, which one?
No, this contribution does not introduce any new dependencies.
What should a reviewer concentrate their feedback on?
make check) continue to pass.query_registry(target="tags")remains the unified interface for tag queries.Any other comments?
N/A
PR checklist
For all contributions
make check).docs/source/.examples/.