-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$reader->setTestAutodetect() not usefull when php version > 8.1 #4092
Comments
It is useful in 8.1+ for anyone who wants to read Csv's with Mac line endings, which is admittedly a small (possibly non-existent) group. That functionality has been marked deprecated, and will disappear when Php stops supporting it, scheduled for Php9. There is no reason to prematurely create a BC break for those users. The test for auto-detect itself should not cause any problems even if you don't need it (messages are suppressed for ini_set and the setting is restored after it is processed). |
No BC break for php version > 8.1 makenthe method Just a dummy and set default to false in ini-set. |
I'm using this. |
What is the problem you are trying to solve? |
Continue using the library in my project without being forced to set false on any reader instance cosebase wide. |
This is:
What is the expected behavior?
To not force the user to set autodetect to false when detected php version is >= 8.1
Simply keep it to false or never set it .
What is the current behavior?
Forced to set false in order to not have problems with deprecation notices
What are the steps to reproduce?
Set true with php >= 8.1 version
If this is an issue with reading a specific spreadsheet file, then it may be appropriate to provide a sample file that demonstrates the problem; but please keep it as small as possible, and sanitize any confidential information before uploading.
What features do you think are causing the issue
Does an issue affect all spreadsheet file formats? If not, which formats are affected?
any software
Which versions of PhpSpreadsheet and PHP are affected?
The text was updated successfully, but these errors were encountered: