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 #1924] [CLOSED] Strong type Value on DataBoundFormComponent<T> #2971

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

📋 Pull Request Information

Original PR: https://github.com/radzenhq/radzen-blazor/pull/1924
Author: @pianomanjh
Created: 1/24/2025
Status: ❌ Closed

Base: master ← Head: task/databoundformcomponent-use-generic-value

📝 Commits (1)

  • 743e742 Strong type Value on DataBoundFormComponent, for more canonical use and consistency, and ease of extension.

📊 Changes

4 files changed (+13 additions, -13 deletions)

View changed files

📝 Radzen.Blazor.Tests/DropDownTests.cs (+1 -1)
📝 Radzen.Blazor/DataBoundFormComponent.cs (+5 -5)
📝 Radzen.Blazor/RadzenAutoComplete.razor.cs (+5 -5)
📝 Radzen.Blazor/RadzenDataGridHeaderCell.razor (+2 -2)

📄 Description

This updates the Value property of DataBoundFormComponent<T> to be of type T, for more canonical use, consistency, and ease of extension.
We have several custom controls that benefit from inheriting from this component, to better fit in the Radzen ecosystem. Needing to cast T when binding in these scenarios causes various difficulties, and is unnecessary as much as I can tell.

This should not result in any breaking changes, as users who are already casting this value to T will simply no longer need to.

Please let me know if I'm missing something as to the need for Value to be object vs T.

🔄 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/1924 **Author:** [@pianomanjh](https://github.com/pianomanjh) **Created:** 1/24/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `task/databoundformcomponent-use-generic-value` --- ### 📝 Commits (1) - [`743e742`](https://github.com/radzenhq/radzen-blazor/commit/743e74238088a737ed8e735bc712c8bfb2611548) Strong type Value on DataBoundFormComponent<T>, for more canonical use and consistency, and ease of extension. ### 📊 Changes **4 files changed** (+13 additions, -13 deletions) <details> <summary>View changed files</summary> 📝 `Radzen.Blazor.Tests/DropDownTests.cs` (+1 -1) 📝 `Radzen.Blazor/DataBoundFormComponent.cs` (+5 -5) 📝 `Radzen.Blazor/RadzenAutoComplete.razor.cs` (+5 -5) 📝 `Radzen.Blazor/RadzenDataGridHeaderCell.razor` (+2 -2) </details> ### 📄 Description This updates the Value property of `DataBoundFormComponent<T>` to be of type `T`, for more canonical use, consistency, and ease of extension. We have several custom controls that benefit from inheriting from this component, to better fit in the Radzen ecosystem. Needing to cast T when binding in these scenarios causes various difficulties, and is unnecessary as much as I can tell. This should not result in any breaking changes, as users who are already casting this value to T will simply no longer need to. Please let me know if I'm missing something as to the need for `Value` to be `object` vs `T`. --- <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:21 +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#2971
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?