There was a bug on the feature page where lineage was retrieved even when not enabled, throwing an error when there was nothing available at the endpoint.
Motivation and Context
Fixes errors when feature lineage is not enabled
How Has This Been Tested?
Ran the code locally and saw the feature lineage API was no longer being called after the change
Documentation
N/A
CheckList
[X] PR title addresses the issue accurately and concisely
Description
There was a bug on the feature page where lineage was retrieved even when not enabled, throwing an error when there was nothing available at the endpoint.
Motivation and Context
Fixes errors when feature lineage is not enabled
How Has This Been Tested?
Ran the code locally and saw the feature lineage API was no longer being called after the change
Documentation
N/A
CheckList