search

codeice / linqtoexcel

Automatically exported from code.google.com/p/linqtoexcel
0 stars 0 forks source link

Feature request: trimming whitespace #81

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create an excel sheet that will be used by humans
2. Manually punching in data might insert unwanted white space
3. Trimming all fields results in many lines of AddTransformation and
   adds a maintenance burden when the sheet is expanded

What is the expected output? What do you see instead?
Either a general method to perform a transformation on all values, or a 
specific one that Trim()s them

What version of the product are you using? On what operating system?
1.6.6 on various primarily on win7 (development) and server 2008 (production).

Please provide any additional information below.
Thanks for an awesome excel reader. I could not imagine that reading from excel 
would be so painless.

Original issue reported on code.google.com by kebonar...@gmail.com on 18 Jan 2013 at 10:49

GoogleCodeExporter commented 8 years ago 
Thanks for the suggestion kebonarjee.

I'm going to pass on this suggestion because I don't think it affects many 
people, and I don't have the bandwidth to make the change myself.

I'm going to close this ticket for now, but if other people also want this 
feature, then please leave a comment. If I get enough comments then I will 
circle back around to it.

And there's always the option to make the change yourself and submit a pull 
request! :-)

Original comment by paulyo...@gmail.com on 5 Feb 2013 at 3:30

GoogleCodeExporter commented 8 years ago 
https://code.google.com/p/linqtoexcel/issues/detail?id=99

I am also feeling the heat of trimming whitespaces. It would be great if we 
have this feature included in this wonderful LinqToExcel.

Original comment by sathya28...@gmail.com on 29 Nov 2013 at 7:09

GoogleCodeExporter commented 8 years ago 
Absolutely would like this as well. A property on the ExcelQueryFactory would 
be most useful for me, since it would cover the LinqToExcel.Row class, but a 
property that could be applied at the class or field level for a generic class 
would be useful too.

Original comment by aa...@sherber.com on 22 Mar 2014 at 6:02

GoogleCodeExporter commented 8 years ago 
Okay, I made the change myself and submitted a pull request!

Original comment by aa...@sherber.com on 23 Mar 2014 at 2:28