alteryx / alteryx/evalml

Update label encoder in pipeline implementation to look for LabelEncoder class instead of looking for "Label Encoder"

未关闭
#2,906 1 条评论 1 个 reaction 已指派 1 人 已被 @asniyaz 认领 在 GitHub 查看
enhancement needs design tech debt
主要语言
Python
星标
850
派生
96
PR 合并指标
30 天内没有已合并 PR

描述

https://github.com/alteryx/evalml/pull/2821/ introduces the label encoder as a component in the pipeline, rather than an attribute. However, we still set a pipeline's `_encoder` attribute to a label encoder in the pipeline, if it's available.

As documented in [this comment](https://github.com/alteryx/evalml/pull/2821/files#r723692569), there is an assumption that the Label Encoder component has a name "Label Encoder". However, we should be more flexible and accept the label encoder even if its name was "my cool label encoder".

One suggestion is to find the component by checking for the component class instead. This work would be made much easier by https://github.com/alteryx/evalml/issues/2878.

One edge case that may be important to think about the case where there may be multiple label encoders. What do we do then?

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。