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 #1647] [CLOSED] Radzensteps onafterchange #2848

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

📋 Pull Request Information

Original PR: https://github.com/radzenhq/radzen-blazor/pull/1647
Author: @iustin94
Created: 8/13/2024
Status: ❌ Closed

Base: master ← Head: radzensteps-onafterchange

📝 Commits (5)

  • 2d69bb0 Added AllowPrevious and AllowNext boolean flags.
  • 74035ed Moved style setting in the code behind file
  • 4d6d6c7 Call style from markdown
  • c39584a Changed button enablement
  • 41c4262 Changed default values

📊 Changes

4 files changed (+112 additions, -2 deletions)

View changed files

📝 Radzen.Blazor/RadzenSteps.razor (+2 -2)
📝 Radzen.Blazor/RadzenSteps.razor.cs (+57 -0)
➕ RadzenBlazorDemos/Pages/StepsAllowPreviousNext.razor (+43 -0)
📝 RadzenBlazorDemos/Pages/StepsPage.razor (+10 -0)

📄 Description

The purpose of this PR is to enable the RadzenSteps component to provide more control over the flow of moving between steps. As well as making more clarity in the logic flow.

Things done:

  • Renamed the CanChange event to BeforeChange: This is becase the CanChange event did not actually prevent the user clicking the change buttons, instead it allowed the button to be clicked and then the event handler had to do something to prevent that from happening.

  • Added AllowPrevious and AllowNext boolean flags: Using these flags, the steps provide more control of when a user can go forward or backwards. This way, a user can be completelly prevented from triggering the previous/next button until they perform a required action in the wizard.

🔄 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/1647 **Author:** [@iustin94](https://github.com/iustin94) **Created:** 8/13/2024 **Status:** ❌ Closed **Base:** `master` ← **Head:** `radzensteps-onafterchange` --- ### 📝 Commits (5) - [`2d69bb0`](https://github.com/radzenhq/radzen-blazor/commit/2d69bb022e153eda049e0a145dfc06d50fe27c06) Added AllowPrevious and AllowNext boolean flags. - [`74035ed`](https://github.com/radzenhq/radzen-blazor/commit/74035ed8f93cfc85ead25ee521ebcd22576c11e4) Moved style setting in the code behind file - [`4d6d6c7`](https://github.com/radzenhq/radzen-blazor/commit/4d6d6c72cd8a569642dfaa17427201a7338d625e) Call style from markdown - [`c39584a`](https://github.com/radzenhq/radzen-blazor/commit/c39584a8bfa9ff964059fb34ec1f9d264ec567ba) Changed button enablement - [`41c4262`](https://github.com/radzenhq/radzen-blazor/commit/41c4262dbcaaeb0e6e511fec487bfe8030b27870) Changed default values ### 📊 Changes **4 files changed** (+112 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `Radzen.Blazor/RadzenSteps.razor` (+2 -2) 📝 `Radzen.Blazor/RadzenSteps.razor.cs` (+57 -0) ➕ `RadzenBlazorDemos/Pages/StepsAllowPreviousNext.razor` (+43 -0) 📝 `RadzenBlazorDemos/Pages/StepsPage.razor` (+10 -0) </details> ### 📄 Description The purpose of this PR is to enable the RadzenSteps component to provide more control over the flow of moving between steps. As well as making more clarity in the logic flow. Things done: - Renamed the CanChange event to BeforeChange: This is becase the CanChange event did not actually prevent the user clicking the change buttons, instead it allowed the button to be clicked and then the event handler had to do something to prevent that from happening. - Added AllowPrevious and AllowNext boolean flags: Using these flags, the steps provide more control of when a user can go forward or backwards. This way, a user can be completelly prevented from triggering the previous/next button until they perform a required action in the wizard. --- <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:20:44 +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#2848
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?