-
Notifications
You must be signed in to change notification settings - Fork 363
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
Add min and max properties to number field #306
Add min and max properties to number field #306
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@jperasmus is attempting to deploy a commit to the Measured Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thanks @jperasmus!
If you have time, would you mind adding it to the demo app for the Columns and Flex components?
If not, don't worry. Once this is merged, I'll add it to the docs.
|
||
```tsx {5,6,10} copy showLineNumbers | ||
const config = { | ||
categories: { | ||
typography: { | ||
components: ["HeadingBlock", "ParagraphBlock"], | ||
label: "Text", | ||
title: "Text", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just added this extra small fix to the docs that I noticed was wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah nice one ty
Made the changes as requested and also updated the docs with a basic example showing the 2 new optional fields. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works beautifully! Thanks for updating the docs and fixing my typos, too!
tl;dr;
Tiny PR to address #270
details
I wasn't sure if it started to make sense to pull the
NumberField
into its own component or add the 2 new props to the existingDefaultField
. Went for the pragmatic approach. Happy to split it out as well if needed.