jbartula

No. The Author of this package needs to update it for the breaking changes in MudBlazor.

It would be nice if you could just make the ` internal CellValue(object? data, CellValueType cellValueType)` constructor public. This would solve the issue. Thanks.

Yes that's a possible alternative, but introduces more code (1 more line per each). I currently just use a second switch at the bottom that calls CellValue.Logical, CellValue.Text, etc. depending...

Thanks.

After the latest update, this bug reappared, with using `CellValue.Text()`.  Hit enter  And it cuts off the zero, despite the cell type being Text

This is a workaround: ``` sheet.Cells.BeforeCellValueConversion += (sender, args) => { if (sheet.Cells[args.Row, args.Column].ValueType == CellValueType.Text) { args.NewValue = CellValue.Text(args.OriginalValue?.ToString() ?? string.Empty); } }; ```

As a workaround, I wrapped the Component in an ErrorBoundary: ``` //sheet here @{ new Task(async () => await _vm.SavePageData().ConfigureAwait(false)).RunSynchronously(); navigationManager.Refresh(true); } ``` But obviously, this is trash. May be...