release of v10.62 #4414
Merged
release of v10.62 #4414
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
To fix failing CI runs. --------- Co-authored-by: -l <anderslangseth@gmail.com>
|
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. |
) I don't think this has any effect, as `auto` was a non-valid value. Here are the [docs](https://developer.mozilla.org/en-US/docs/Web/CSS/min-width).
The main reason was due to a missing `await`. My bad. It did [fail here](https://github.com/dnbexperience/eufemia/actions/runs/12377018356/job/34554639319?pr=4414).
…#4409) This PR adds two new properties to the `SubmitIndicator`: - `showLabel` makes to the label gets visible. - `label` is to customize the label content. The `SubmitIndicator` is not effected from this change, except that we speed up the animation. --------- Co-authored-by: Anders <anderslangseth@gmail.com>
…es (#4410) This PR is based on #4409 Add `showLabel` to the FieldBlock, so that async processes have label instead of just the dots: <img width="420" alt="Screenshot 2024-12-17 at 10 35 02" src="https://github.com/user-attachments/assets/df772014-aa63-4959-b7f1-b936eb0eb0b1" /> --------- Co-authored-by: Anders <anderslangseth@gmail.com>
Like the `update` method from useData, I think it would be befeifial to
have an update method to use "outside" of the React tree. Right now I
think it is logical to place in the setData handler. But any better
ideas are welcome.
```tsx
import { Form } from '@dnb/eufemia/extensions/forms'
const myFormId = 'unique-id' // or a function, object or React Context reference
const { update } = Form.setData(myFormId)
// Call "update" with the path and the new value.
update('/foo', 1)
```
…bers` (#4419) fixes #4293 As of now, I've just added support for the characters ÆØÅ, not sure if there's other non-alphanumeric characters we should support, and perhaps improve the regex to something better than just`\wÆØÅæøå`. [Original CSB from the issue](https://codesandbox.io/p/sandbox/stoic-feather-8ymh7s) [CSB with the fix](https://codesandbox.io/p/sandbox/relaxed-paper-gyxyf8?workspaceId=ws_LbiDwJdEBdbwxH2AkyAyVE) using commit aa28f0c [CSB with the fix](https://codesandbox.io/p/sandbox/flamboyant-feistel-klw9c2?workspaceId=ws_LbiDwJdEBdbwxH2AkyAyVE) using commit 2334c87 --------- Co-authored-by: Tobias Høegh <tobias@tujo.no>
Changelog for forms in release v10.62.0 #4414 --------- Co-authored-by: Tobias Høegh <tobias@tujo.no>
tujoworker
approved these changes
Dec 20, 2024
|
🎉 This PR is included in version 10.62.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.