You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After upgrading my Nuget to1.14.0 the project no longer works in runtime, I'm having a pure web-assembly app.
The error goes away if I rollback the version to 1.13.1, and re-appears if I redo the upgrade, so its consistent.
I have noticed the added "Localization" dependency in the new version, I'm trying to keep my footprint small, so I wonder what is added in the new version.
I'm having the same error on multiple tables, so it fails consistently as well.
To Reproduce
Nuget install 1.14.0
Clean solution
Build
Reverse this to rollback.
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: Cannot provide a value for property 'Localization' on type 'BlazorTable.Table`1[[***.Models.User, ***.Models, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]]'. There is no registered service of type 'Microsoft.Extensions.Localization.IStringLocalizer`1[BlazorTable.Components.Localization]'.
System.InvalidOperationException: Cannot provide a value for property 'Localization' on type 'BlazorTable.Table`1[[***.Models.User, ***.Models, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]]'. There is no registered service of type 'Microsoft.Extensions.Localization.IStringLocalizer`1[BlazorTable.Components.Localization]'.
Expected behavior
To not have critical exceptions
The text was updated successfully, but these errors were encountered:
Describe the bug
After upgrading my Nuget to1.14.0 the project no longer works in runtime, I'm having a pure web-assembly app.
The error goes away if I rollback the version to 1.13.1, and re-appears if I redo the upgrade, so its consistent.
I have noticed the added "Localization" dependency in the new version, I'm trying to keep my footprint small, so I wonder what is added in the new version.
I'm having the same error on multiple tables, so it fails consistently as well.
To Reproduce
Reverse this to rollback.
Expected behavior
To not have critical exceptions
The text was updated successfully, but these errors were encountered: