Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: small storybook and docs updates to SensitiveText component (#…
…28089) ## **Description** This PR updates the Storybook stories for the `SensitiveText` component to align with extension component library standards. The changes include: - Updating Storybook stories to use the CSF 3.0 format for better organization and future-proofing. - Converting `README.md` to `README.mdx`, leveraging Storybook stories for documentation and improving the accessibility and usability of the component documentation. [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/28089?quickstart=1) ## **Related issues** Related: #28021 ## **Manual testing steps** 1. Run Storybook locally and navigate to the `SensitiveText` component. 2. Verify that the stories render correctly in the CSF 3.0 format. 3. Check that the new `README.mdx` renders properly in the Storybook Docs tab. ## **Screenshots/Recordings** ### **Before** https://github.com/user-attachments/assets/e1804283-72d2-45e6-829b-e2ce38776e1e ### **After** https://github.com/user-attachments/assets/5d776529-6fe3-4646-90f2-57f2ceceefd6 ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/CODING_GUIDELINES.md). - [x] I’ve completed the PR template to the best of my ability. - [x] I’ve included tests if applicable. - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable. - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-extension/blob/develop/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I’ve manually tested the PR (e.g., pulled and built the branch, ran the app, tested the code being changed). - [ ] I confirm that this PR addresses all acceptance criteria and includes the necessary testing evidence, such as recordings or screenshots.
- Loading branch information