Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The PipelineML extract_pipeline_catalog should be private #100

Closed
Galileo-Galilei opened this issue Oct 20, 2020 · 0 comments · Fixed by #101
Closed

The PipelineML extract_pipeline_catalog should be private #100

Galileo-Galilei opened this issue Oct 20, 2020 · 0 comments · Fixed by #101
Assignees
Labels
bug Something isn't working
Milestone

Comments

@Galileo-Galilei
Copy link
Owner

Description

The PipelineML extract_pipeline_catalog method should be private. Indeed it is never intended to be used directly by the user, unlike extract_pipeline_artifact.

Context

The documentation and code suggest the user can used extract_pipeline_catalog when they should ot use it directly. extract_pipeline_artifacts should be used instead.

Solution

Rename extract_pipeline_catalog to indicate it is private.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant