Storybook for PCF Controls - Part 1 : Set the Story Straight
In the frontend development world, Storybook as emerged as the industry standard to showcase and test UI components.
In this series of posts I will show how easy (and rewarding) it is to implement and publish a Storybook for a PowerApps Component Framework (PCF) project. That way users can have a direct and interactive access to the control without having to install anything on their side.
- Part 1, will focus on setting up Storybook and write the stories in the context of a PCF control project.
- Part 2, will demontrate how to publish the Storybook to Github Pages on every commit using GitHub Actions.
What is Storybook
In essence, Storybook is a framework that helps web developers express and test frontend workflows. It can be used for building, documenting, and testing UI components in isolation.
Published on:
Learn moreWe can help you with Storybook for PCF Controls - Part 1 : Set the Story Straight
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
PCF Controls Tips & Tricks: How to Bundle and Resolve Static JSON Files
JSON files are one of the most common and convenient ways to store structured data. They’re lightweight, human-readable, and easy to parse in ...
PCF Controls Tips and Tricks : How to skip Linting at Build-Time
Have you ever been unable to properly build a PCF control because of linting errors? Well, lately I have, and it can get really frustrating. E...
PCF Controls Tips & Tricks : How to detect Authoring Mode
When you configure a PCF control on a Dataverse model-driven app, the form designer will try to render the control even though it’s not ...
How to Create Deep Links to D365 F&O Records with Dataverse Virtual Tables
It is a common requirement for SaaS platform that exposes form over data to be able to share a secure link (a.k.a. Deep Link) to access a give...
Model-Driven App Trick : How to Hide a Ribbon Button when the Form is Dirty
I recently encountered a requirement on a model-driven app project to display a custom ribbon button only when the form had no unsaved changes...