oleibman on master
Respect DataType in insertNewBe… (compare)
oleibman on master
Fixes #2430 (#2431) * Handle a… (compare)
tests. I don't mind all that much, but I thought if you don't have any specific reason it might be nice to be coherent with PhpOffice projects
@MarkBaker thanks for your reply on PHPOffice/PhpSpreadsheet#788 do you think that it is feasible to "hack" the stack based parser in order to give a specific processing to IF calls ?
I am deep in
processTokenStack(), still trying to figure what's happening around. If you think it is close to impossible to implement something without generating side effects I will stop there.
given an existing xlsx file with lots of formulas and formatting
i want to add some data and write it to a new file.
currently it breaks Formulas and Formatting in the output, even without changes.
$spreadsheet = \PhpOffice\PhpSpreadsheet\IOFactory::load('complextemplate.xlsx'); $writer = \PhpOffice\PhpSpreadsheet\IOFactory::createWriter($spreadsheet, 'Xlsx'); $writer->save("output.xlsx");
Is there a more unobstrusive way of adding data to an existing XLSX File? (Also open for suggestions of other tools / libraries)
Just reading and writing the file results in a corrupted result. Just wondering whether or not i am missing an option or something from the docs to make changes to a file without recreating it complete within PhpSpreadsheet.
Hi, I am observing that if A2 contains
=HLOOKUP(A1, D1:AC120, 3, FALSE), it works fine if unused lines in the range are using A2 (which otherwise would be a circular reference). Which is consistent with the behavior of spreadsheet software.
But I don't get in the code which part of the calculation engine is handling that and I am observing a bug related to this. One of the "would-be" circular reference is resolved to some value, used in another result that is then cached and retrieved later ... without a proper recomputation.
developmentVersion2branch for working on updating for the newer features of PHP7
#NA!, etc); though the function code can be improved as a result of that change
@MarkBaker we should definitely go with PHP 7.1, otherwise type hinting cannot be as useful as it should be.
For branching I was considering keeping only
master branch as a permanent branch. I noticed that
develop is not really useful because it should be as stable as possible anyway. So we could just as well merge into master directly (and release from time to time as usual). This simplify our workflow, avoid confusion for new contributors and avoid accidental branch diverging as it happened when releasing 1.5.2.
I saw you closed PHPOffice/PhpSpreadsheet#818 this won't be merged ?