Add a DeprecationWarning about deprecating the list API for ComponentGraphs#2488
Add a DeprecationWarning about deprecating the list API for ComponentGraphs#2488angela97lin merged 4 commits intomainfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2488 +/- ##
=======================================
+ Coverage 99.7% 99.7% +0.1%
=======================================
Files 283 283
Lines 25571 25585 +14
=======================================
+ Hits 25469 25483 +14
Misses 102 102
Continue to review full report at Codecov.
|
| self.component_graph = ComponentGraph().from_list( | ||
| component_graph, random_seed=self.random_seed | ||
| ) | ||
| with warnings.catch_warnings(): |
There was a problem hiding this comment.
I added this here to filter for the DeprecationWarning because users who are using AutoMLSearch or PipelineBase might be confused as to why they're receiving this. I think the warning should only surface if the user directly initializes a ComponentGraph using a list directly, Pipelines should still handle lists of components :)
jeremyliweishih
left a comment
There was a problem hiding this comment.
nice! I like the warning catch.
| self.component_graph = ComponentGraph().from_list( | ||
| component_graph, random_seed=self.random_seed | ||
| ) | ||
| with warnings.catch_warnings(): |
Closes #2483