Sajid Alam
08/05/2024, 10:03 AMenable
or disable
the preview for all datasets in their local Kedro-Viz instance or when publishing Kedro-Viz from the CLI or UI.
We've made significant enhancements to Kedro-Viz, enabling it to be used as a standalone React component. The documentation has been updated to include a new section dedicated to using Kedro-Viz as a standalone React component, more details can be found in the NPM documentation. Lastly several 🪲bug fixes are outlined in the release notes. You can check out the demo.
🚀 What can you expect in this release?
• `Enable`/`disable` preview for all datasets when publishing Kedro-Viz from the CLI and UI, providing greater control over dataset visibility.
• Display published URLs.
• Conditionally move session store and stats file to .viz
directory.
• Introduce metadataPanel
in display
prop in Kedro-Viz react component.
• Refactor namespace pipelines.
• Expose the internal Redux state through options
prop while using Kedro-Viz as a React component.
• Enhance documentation for the Kedro-Viz standalone React component.
• Add Datasets preview toggle in the settings panel.
🪲 Bug fixes and other changes:
• Relax packaging
pin in requirements.
• Add favicon to kedro-viz documentation.
• Add "-p" flag to kedro-viz to match kedro run.
• Fix bug related to nested namespace pipelines.
• Migrate from toposort
to graphlib
.
• Fix packaging.
• Adjust requirements file and dependabot versioning strategy.
• Refactor CommandCopier component.
• Set isPrettyName
toggle to False by Default.
• Add -p
argument option for kedro viz
to align with kedro pipeline options.
• Replace data-heap-event
with standardised data-test
for Cypress and Telemetry.
Community contributions:
A big thank you to Vlad Cozma and Yuri Fedotov for contributing to this release!
How do I get the latest release?
• Python: pip install kedro-viz==9.2.0
• React: npm install @quantumblack/kedro-viz@latest
You too can contribute by using these features and providing feedback. Follow our roadmap for more updates, comment on the tickets, and suggest future features to the community.
Until next time,
The Kedro Team