-
-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
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
MatBlazor.MatTextField requires a value for the 'ValueExpression' parameter. [1.5.3] #184
Comments
I will check today |
I upgraded to the latest MatBlazor 1.5.3 version as well, and immediately experienced the broken TextField component, as described above. I needed to downgrade to 1.5.2 again. Looking forward to the fixed version. |
Hey! |
I can confirm the issue is gone in 1.5.4. I have tested with restart the project to see if I need to refresh again, which to my surprise, I don't need to. But it might be worth to note it down anyway, in case people are experienced the cache issue. |
This issue is back in version 1.6 |
Occurs when some MatBlazor components are used inside EditForm. Example:
warn: Microsoft.AspNetCore.Components.Web.Rendering.RemoteRenderer[100] |
Any solution? Still happens to me in the latest version |
This is still present in the latest version if you use (In my case with the Checkbox) Value="@SomeValue" ValueChanged="@(e => ValueChanged(e))" together... |
I'm having the same problem using MatAutocompleteList
I also tried
I'm using MatBlazor 2.0.0 installed from Nuget. |
I'm having same issue, too with MatSelect. |
I'm having this issue with MatSelectValue and EditForm in 2.1.0 |
Hello, we have the same issue with MatCheckbox... (by using Value and ValueChanged attributes... Meanwhile, when we deleted the tag that was surrounding our components, it solved the problem. The MatChackbox element could not be bound to the form. |
Still happening with MatSelect's in latest release. |
Here is workaround approach I used: https://docs.telerik.com/blazor-ui/knowledge-base/value-changed-validation-model |
@tkennedy13 the issue should be resolve with the latest code in "develop" for AutoComplete. @sandrohanea can you take a look and see if your solution will work here? |
Indeed, it should be fixed for AutoComplete but the fix was isolated there. If the |
I am experiencing the same issue on a MatSelect with latest package 2.7.0 (I need to realize 2 cascading matselects, e.g. the selected value from the first matselect updates the second matselect)...here follows my code...does anybody know a workaround ?
code behind
Error:
|
In the newest update 1.5.3, I got this error "MatBlazor.MatTextField requires a value for the 'ValueExpression' parameter. Normally this is provided automatically when using 'bind-Value'."
The bug show up whenever an component are using textfield.
The bug should only show if MatTextField do not contain an value.
I am using basic authorizeView with EditForm in my code, and as you can see, MatTextField do have bind-values which means they contains values, so I am guessing the cause must be related to ValueExpression in the BaseMatInputComponent. Because the error message only show up if ValueExpression is null.
The code is working fine in 1.5.2 update.
I hope someone can find an fix for that bug, because it's currently breaking a lot of components.
The text was updated successfully, but these errors were encountered: