release of v10.56 #4257
Merged
release of v10.56 #4257
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nth` when `endMonth` prop is defined (#4254)
) As of today the following elements DL, UL, OL [say they have support](https://eufemia.dnb.no/uilib/elements/lists/properties/#ol-properties) for skeleton and skeletonMethod, but they don't as they internally in the component/element set skeleton to false(`skeleton=false`). This PR removes docs and type support for skeleton(as it is not actually supported) in: - Dl - Ul - Ol
|
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. |
Fixes: ``` Browserslist: caniuse-lite is outdated. Please run: npx update-browserslist-db@latest Why you should do it regularly: https://github.com/browserslist/update-db#readme ```
Co-authored-by: Tobias Høegh <[email protected]>
- Ignore Form.Visibility - Show given props in message, so it is possible to find the source/cause of the message.
This is not correct/finished. The motivation behind this change is that when reading the [description](https://eufemia.dnb.no/uilib/extensions/forms/Form/Appearance/info/#description), I don't easily understand which Field.X-components I can use or not with the `Form.Appearance`. The description doesn't use commonly known names in the forms world as base fields or feature fields, etc, but it rather says `provides theming of sizes of input fields, including Autocomplete and Dropdown`, thoughts: - What's input fields? - Why do we mention the base Eufemia component Autocomplete, instead of the Field equivalent? - Why do we mention the base Eufemia component Dropdown, instead of the Field equivalent? --------- Co-authored-by: Tobias Høegh <[email protected]>
…those with snake case (#4273) Co-authored-by: Tobias Høegh <[email protected]> Co-authored-by: Anders <[email protected]>
<img width="231" alt="Screenshot 2024-11-15 at 11 02 16" src="https://github.com/user-attachments/assets/653bfc1a-e010-4b4d-a205-b498497e6976">
Co-authored-by: Joakim Bjerknes <[email protected]> Co-authored-by: Tobias Høegh <[email protected]>
…s given by an array (#4284)
…file handling during upload (#4281) Add support for asynchronously processing/handling files so a virus checker can be used with the Field.Upload component. --------- Co-authored-by: Whitney Hiltz <[email protected]>
…lt (with option to open in Dialog) (#4282) This PR changes the existing behavior of the `help` prop for Fields that previously supported it. The content now opens inline instead of in a Dialog. The `help` prop has now all of these optional props: ```tsx <Field.String label="Label text" help={{ title: 'Help is available', content: 'Take the time to help other people without expecting a reward or gratitude is definitely important in living an optimistic life.', open: false,// only for the inline variant renderAs: 'dialog' }} /> ``` We use this prop description: > Provide help content for the field using `title` and `content` as a string or React.Node. Additionally, you can set `open` to `true` to display the inline help or use `renderAs` set to `dialog` to render the content in a [Dialog](/uilib/components/dialog/) (recommended for larger amounts of content). Examples with inline "HelpButton": - [FieldBlock](https://eufemia-git-feat-forms-inline-help-button-eufemia.vercel.app/uilib/extensions/forms/create-component/FieldBlock/demos/#inline-help-button-vertical-only) (several examples) - [Form.MainHeading](https://eufemia-git-feat-forms-inline-help-button-eufemia.vercel.app/uilib/extensions/forms/Form/MainHeading/#with-helpbutton) - [Form.SubHeading](https://eufemia-git-feat-forms-inline-help-button-eufemia.vercel.app/uilib/extensions/forms/Form/SubHeading/#with-helpbutton) - [Field.String](https://eufemia-git-feat-forms-inline-help-button-eufemia.vercel.app/uilib/extensions/forms/base-fields/String/#with-help) - [Field.Number](https://eufemia-git-feat-forms-inline-help-button-eufemia.vercel.app/uilib/extensions/forms/base-fields/Number/#with-help) - [Field.Upload](https://eufemia-git-feat-forms-inline-help-button-eufemia.vercel.app/uilib/extensions/forms/feature-fields/more-fields/Upload/#with-help) - ... many other fields do have an example as well. **NB:** We do not document the internals of the inline version at this time. This can be included in another PR. The reason is that it would require additional tests, examples, and documentation. It is also an "isolated" feature specific to the HelpButton. However, as of this writing, I am unsure if we will ever document it, as integration is not straightforward. There are several considerations to address when implementing it.
- [x] Add documentation - [x] Add some tests - [x] Double check if any of the props needs accommodate for field props - [x] Fix startMonth and endMonth bugs - [x] Fix date correction test - [x] Merge `DatePicker` camelCase changes --------- Co-authored-by: Tobias Høegh <[email protected]> Co-authored-by: Anders <[email protected]>
|
🎉 This PR is included in version 10.56.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.