-
Notifications
You must be signed in to change notification settings - Fork 32
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
release of v10.14 #2906
release of v10.14 #2906
Conversation
The change: When the user changes the countryCode value – without making a "selection" – and then the input blurs, it will show the current selected value. This way, it will not be possible to "clear" a country code or add a custom. But that also requires us to deliver all possible available codes. The error rate will be way lower for sure. Now, its more like a Dropdown, but with fee text search ability. Here's [a demo](https://eufemia-git-feat-phone-number-keep-value-eufemia.vercel.app/uilib/extensions/forms/feature-fields/PhoneNumber/demos/).
…rops (#2882) Fix limitations in the handling of changed external props, as well as the prioritization between different error sources.
This way we can simply list props that are not supported for various reasons: ```mdx <DataValueReadwriteProperties type="string" omit={[ 'layout', 'label', 'labelDescription', 'labelSecondary', 'emptyValue', ]} /> ```
Adds card stories, using fields from forms extension. THOUGHTS: Seems like my stories is not working as expected as of right now, as I'm doing: ``` <Card stack> <> ...component1 ...component2 </> </Card> ``` And must rather do the following for it to work: ``` <Card stack> ...component1 ...component2 </Card> ``` Should/could the first example with React fragment(`<></>`) work? -------------------------------------------------------------------------------- Added one more commit where I duplicate it, instead of sharing it, to make it work/look as expected. --------- Co-authored-by: Tobias Høegh <[email protected]>
With that change we increase the number of affected files from 30 to 80.
Co-authored-by: Anders <[email protected]> Co-authored-by: Tobias Høegh <[email protected]>
FieldBlock did not receive errors from initial renders of inner field components, only after change callbacks to the value.
Sbanken theming of the Radio component. A fairly significant number of CSS variables has been introduced here. I've put them in a mixin in order to avoid listing all these variables in three different sass files (default, ui and sbanken theme files), but I am far from sure this is the best way to approach this, so please share your thoughts on this upon review.
Errors based on schema validation in the Provider did not get values injected when providing custom error messages. This is now handeled by adding validation values to the error object (when validated in the Provider) and injecting them in the target field component with their specific error messages. With test to ensure it works as intended.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit ef83713:
|
Interested in a release of this, as I consider the following fix #2905 quite important, as without that the following components don't work with SWC in Vite.js:
|
🎉 This PR is included in version 10.14.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
No description provided.