feat: Enhance IDataReader export with DynamicColumnFirst and Custom Formatting Delegate #700
+70
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When exporting using
IDataReader
, I noticed that even when passingDynamicColumn
, the exported content was not being exported according to the passed data.In this PR, the following adjustments have been made for exporting using
IDataReader
:DynamicColumnFirst
property to the configuration, which ensures that the data inDynamicColumn
is used as the standard for exporting (currently only handled forIDataReader
). To avoid breaking changes and unexpected behavior, this configuration item is added with a default value offalse
.ExcelColumnInfo
andDynamicColumn
.GetColumnInfosFromDynamicConfiguration
to filterDynamicColumn
in a case-insensitive manner.When exporting data, some data is not directly obtained from the database. Therefore, a custom formatting delegate method has been added to format the data.