Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Do we have a compelling reason to enforce tags? #18798

Copy link
Copy link
Open
@thomasjpfan

Description

@thomasjpfan
Issue body actions

With #18797 we are making tags an optional requirement for third-party estimators. If there was a compelling reason to adopt tags, I would think that third-party developers would adopt it.

Currently, the tags are use to hold the metadata of an estimator. This is mostly use in our estimator checks.

One of the selling points is that the tags can replace the attributes we have in our estimators. We recently deprecated _pairwise attribute in #18143 . We are also working on deprecating _estimator_type in #17806. In this point of view, the tags provide a namespace for provided metadata in estimators, which can be used by other libraries that ingest estimators.

Are there any other reasons for third party developers to adopt tags?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.