We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using the sample demo code, we have this code:
<FluentWizard Id="customized-wizard" @bind-Value="@Value" StepTitleHiddenWhen="@GridItemHidden.XsAndDown" Height="300px">
and this in the code block:
@code { int Value = 0; }
when clicking 'Next' button in the wizard, the Value stays at 0. The ValueChanged callback method is never called.
add this line over the FluentWizard:
@Value
The Value variable follow the step currently displayed
The Value variable is always 0 and never change.
just add this code before line 183 in the Microsoft.FluentUI.AspNetCore.Components/Components/Wizard/FluentWizard.razor.cs
await ValueChanged.InvokeAsync(targetIndex);
I tried to create a pull request, but had no success with Git in my Visual Studio ! sorry!
The text was updated successfully, but these errors were encountered:
Thanks for your work. I fixed this in this PR #1538 which will be included in the next release.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
🐛 Bug Report
Using the sample demo code, we have this code:
and this in the code block:
when clicking 'Next' button in the wizard, the Value stays at 0. The ValueChanged callback method is never called.
💻 Repro or Code Sample
add this line over the FluentWizard:
🤔 Expected Behavior
The Value variable follow the step currently displayed
😯 Current Behavior
The Value variable is always 0 and never change.
Fix:
just add this code before line 183 in the Microsoft.FluentUI.AspNetCore.Components/Components/Wizard/FluentWizard.razor.cs
I tried to create a pull request, but had no success with Git in my Visual Studio ! sorry!
The text was updated successfully, but these errors were encountered: