-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs[DST-572]: Form field guidelines #4174
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 0dee034 The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
Coverage report
Show files with reduced coverage 🔻
Test suite run success570 tests passing in 78 suites. Report generated by 🧪jest coverage report action from 0dee034 |
@OsamaAbdellateef can you edit the title of the PR so its containing the issue and the type of change? |
@OsamaAbdellateef also changeset is missing |
I reviewed. Someone else maybe should also: @sebald @marcelkoehler @tirado-rx @KadaStrophe ? |
Description
Our form field components share many common features, such as states (disabled, error, readonly) and functionality (label, control, help text). When we revise every single page, this information would be duplicated across multiple component pages, leading to redundancy and potential inconsistencies.
As we are in the process of revising our component pages, now is the perfect time to implement this solution. Establishing a centralized page will streamline future revisions, ensuring consistency and saving time as we update and maintain our documentation.
What should be tested?
Reviewers:
@marigold-ui/developer