Alternative to accessing attributes of KedroContext after 0.18.0 #808
Replies: 4 comments
-
Hi @willashford - we talked about how the Context has become too bloated in this webinar last week, will get back to you on where those specific attributes will live in 0.18.0 |
Beta Was this translation helpful? Give feedback.
-
Hi @willashford , the majority of the currently deprecated properties can be found in from kedro.framework.project import pipelines, settings
# you might need to also import `from kedro.framework.startup import bootstrap_project` and call it for your tests
|
Beta Was this translation helpful? Give feedback.
-
A bit more context about |
Beta Was this translation helpful? Give feedback.
-
FYI - I'm going to convert this to a discussion |
Beta Was this translation helpful? Give feedback.
-
Introduction
I'm looking to understand the preferred methods of accessing KedroContext attributes for testing purposes after 0.18.0, as I receive a deprecation warning.
Background
As part of managing a kedro project, I like to have tests that check attributes like the pipeline or catalog for coherence to naming conventions, etc. This is typically done via creating a kedro context object as a test fixture and running tests against the objects attributes.
Problem
When I do this currently, I'm presented with a warning about deprecation of accessing these attributes (app name, pipeline, etc) after 0.18.0. What is the preferred approach to accessing these attributes in a future proof way?
Beta Was this translation helpful? Give feedback.
All reactions