starred/radzen-blazor
1
0
Fork 0
mirror of https://github.com/radzenhq/radzen-blazor.git synced 2026-02-04 05:35:44 +00:00
Code Issues 1.3k Packages Projects Releases 22 Wiki Activity

[PR #2179] [MERGED] fixes: Let all DataBoundFormComponent's expose value as TValue #2175 #3112

New Issue
Closed
opened 2026-01-29 18:21:58 +00:00 by claunia · 0 comments
claunia commented 2026-01-29 18:21:58 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/radzenhq/radzen-blazor/pull/2179
Author: @joriverm
Created: 6/10/2025
Status: ✅ Merged
Merged: 6/11/2025
Merged by: @enchev

Base: master ← Head: fixes/BoundValueType

📝 Commits (1)

  • d362e5f fixes: Let all DataBoundFormComponent's expose value as the actual type that it is

📊 Changes

4 files changed (+27 additions, -25 deletions)

View changed files

📝 Radzen.Blazor.Tests/DropDownTests.cs (+6 -7)
📝 Radzen.Blazor/DataBoundFormComponent.cs (+9 -5)
📝 Radzen.Blazor/RadzenAutoComplete.razor.cs (+11 -12)
📝 Radzen.Blazor/RadzenDataGridHeaderCell.razor (+1 -1)

📄 Description

demo pages seemed to work fine, and the breaking change i can think of is when a user would set TValue to anything that isn't object, but use a one way binding to a variable of type object.

i just noticed this as i was investigating SelectedItem and how to use it in our new application

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/radzenhq/radzen-blazor/pull/2179 **Author:** [@joriverm](https://github.com/joriverm) **Created:** 6/10/2025 **Status:** ✅ Merged **Merged:** 6/11/2025 **Merged by:** [@enchev](https://github.com/enchev) **Base:** `master` ← **Head:** `fixes/BoundValueType` --- ### 📝 Commits (1) - [`d362e5f`](https://github.com/radzenhq/radzen-blazor/commit/d362e5fc764854d59b99e6eb87d6a4abfceda015) fixes: Let all DataBoundFormComponent's expose value as the actual type that it is ### 📊 Changes **4 files changed** (+27 additions, -25 deletions) <details> <summary>View changed files</summary> 📝 `Radzen.Blazor.Tests/DropDownTests.cs` (+6 -7) 📝 `Radzen.Blazor/DataBoundFormComponent.cs` (+9 -5) 📝 `Radzen.Blazor/RadzenAutoComplete.razor.cs` (+11 -12) 📝 `Radzen.Blazor/RadzenDataGridHeaderCell.razor` (+1 -1) </details> ### 📄 Description demo pages seemed to work fine, and the breaking change i can think of is when a user would set TValue to anything that isn't object, but use a one way binding to a variable of type object. i just noticed this as i was investigating SelectedItem and how to use it in our new application --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-29 18:21:58 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#3112
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?