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
{{ message }}
Repository navigation
Commit 8fd3e38
Browse filesBrowse the repository at this point in the historyBrowse files
Renaming the "new" MiniExcel class to MiniExcelV2 (#1010)
* Renamed MiniExcelLib.MiniExcel class to MiniExcelV2
This change was adopted to avoid confusion with the `MiniExcelLibs.MiniExcel` facade class containing the V1 methods' signatures. Users will be able to unambiguosly distinguish between the legacy facade methods and the new idiomatic ones.
* Added summary to the MiniExcel facade class
The remarks explain the purpose of the class and advise the consumers of the library to favor the usage of the new `MiniExcelV2` class instead for a better user experience.
* Updated docs to reflect last changes and fixed a few minor mistakes
* Clarified the difference between the `MiniExcel` and `MiniExcelV2` classes in the upgrade notes
- Support for .NET Framework 4.5 was dropped, the minimum supported Framework version is now 4.6.2.
4
-
- The root namespace was changed from `MiniExcelLibs` to `MiniExcelLib`.
5
-
- Instead of having all methods being part of the `MiniExcel` static class, the functionalities are now split into 3 providers:
6
-
`MiniExcel.Importers`, `MiniExcel.Exporters` and `MiniExcel.Templaters` will give you access to, respectively, the `MiniExcelImporterProvider`, `MiniExcelExporterProvider` and `MiniExcelTemplaterProvider`.
4
+
- The root namespace was changed from `MiniExcelLibs` to `MiniExcelLib`; there is also a new entry point to the library, the static class `MiniExcelV2`. The original class has been turned into a facade for backwards compatibility reasons (more on that later).
5
+
- Instead of having all methods being part of a single static class, the functionalities are now split into 3 providers:
6
+
`MiniExcelV2.Importers`, `MiniExcelV2.Exporters` and `MiniExcelV2.Templaters` will give you access to, respectively, the `MiniExcelImporterProvider`, `MiniExcelExporterProvider` and `MiniExcelTemplaterProvider`.
7
7
- This way Excel and Csv query methods are split between the `OpenXmlImporter` and the `CsvImporter`, accessible from the `MiniExcelImporterProvider`.
8
8
- The same structure was adopted for export methods through `OpenXmlExporter` and `CsvExporter`, while template methods are instead currently only found in `OpenXmlTemplater`.
9
9
- OpenXml and Csv methods are only available if the respective `MiniExcel.OpenXml` and `MiniExcel.Csv` packages are downloaded, or if the complete `MiniExcel` package is installed.
10
10
- You can only access the conversion methods `ConvertCsvToXlsx` and `ConvertXlsxToCsv` from the `MiniExcelConverter` utility class, which is part of the full MiniExcel package.
11
-
- If the full MiniExcel package is downloaded, the previous namespace will coexist along the new one, containing the original static methods' signatures, which have become a facade for the aferomentioned providers.
11
+
- If the full MiniExcel package is downloaded, the previous namespace will coexist along the new one, containing a facade `MiniExcel`static class with all the original methods' signatures for backwards compatibility.
12
12
-`IConfiguration` is now `IMiniExcelConfiguration`, but most methods now require the proper implementation (`OpenXmlConfiguration` or `CsvConfiguration`) to be provided rather than the interface
13
-
- MiniExcel now fully supports asynchronous streaming the queries,
13
+
- MiniExcel now fully supports asynchronously streaming the queries,
14
14
so the return type for `OpenXmlImporter.QueryAsync` is `IAsyncEnumerable<T>` instead of `Task<IEnumerable<T>>`
15
15
- When applying a template, unlike version 1.x, the flag for overwriting an already existing file must be provided explicitly.
16
-
-`leaveOpen` parameter has been added to most methods that take a stream as input in both `OpenXmlImporter` and `CsvImporter` to configure whether the stream must be disposed after the operation performed is completed.
17
-
-`useHeaderRow` parameter in multiple `OpenXmlImporter` methods has been renamed to `hasHeaderRow` for making its usage clearer.
16
+
-A `leaveOpen` parameter has been added to most methods that take a stream as input in both `OpenXmlImporter` and `CsvImporter` to configure whether the stream must be disposed after the operation performed is completed.
17
+
-The `useHeaderRow` parameter in multiple `OpenXmlImporter` and `CsvImporter` methods has been renamed to `hasHeaderRow` for making its usage clearer.
18
18
-`CsvExporter.Export` API methods, not being required to return the same type of `OpenXmlExporter.Export`, now return `int` instead of `int[]`.
19
-
- Most `OpenXmlImporter` and `CsvImporter` methods that take a stream as input now take an additional `leaveOpen` boolean parameter, to set to `true` explicitly if you want the stream to be left open at the of the operation.
0 commit comments