Support pageOrder in page setup for Xlsx/Xls Readers/Writers, and implement basic page setup support for other Readers/Writers

[MarkBaker]

This is:

- [ ] a bugfix
- [X] a new feature

Checklist:

• Changes are covered by unit tests
• Code style is respected
• PR Description message explains why the change is made (see https://github.com/erlang/otp/wiki/Writing-good-commit-messages) and what has been added
• CHANGELOG.md contains a short summary of the change
• Documentation is updated as necessary

Why this change is needed?

Simple resolution for Issue #1528

Page Order implemented for:

• Xlsx Reader and Writer
• Xls Reader and Writer

Basic page setup also implemented for:

• Ods Reader
  • Orientation
  • Scale
  • Horizontal/Vertical Centering
  • Page Order
  • Page Margins
• Gnumeric Reader
  • Orientation
  • Scale
  • Horizontal/Vertical Centering
  • Page Order
  • Page Margins
• Xml Reader
  • Orientation
  • Scale
  • Horizontal/Vertical Centering
  • Page Order
  • Page Margins

[PowerKiKi]

@MarkBaker I see you regularly commit code style changes because of PHP-Cs-Fixer. Locally I use a git hook to automatically apply code style before committing. Avoiding the hassle of doing that manually. I suggest you set up something similar, so you can focus on more important things.

My setup is in .git/hooks/pre-commit:

#!/bin/bash

pass=true

files=$(git diff --cached --name-only --diff-filter=ACMR | grep -E '\.(php|phtml)$')
if [ "$files" != "" ]; then

    # Run php syntax check before commit
    while read -r file; do
        php -l "$file"
        if [ $? -ne 0 ]; then
            pass=false
        fi
    done <<< "$files"

    # Run php-cs-fixer validation before commit
    echo "$files" | xargs ./vendor/bin/php-cs-fixer fix --diff --config .php_cs.dist
    if [ $? -ne 0 ]; then
        pass=false
    fi

    # Automatically add files that may have been fixed by php-cs-fixer
    echo "$files" | xargs git add
fi

if $pass; then
    exit 0
else
    echo ""
    echo "PRE-COMMIT HOOK FAILED:"
    echo "Code style validation failed. Please fix errors and try committing again."
    exit 1
fi

[PowerKiKi]

Same remark as the other PR. Shall we try to use \PhpOffice\PhpSpreadsheetTests\Functional\AbstractFunctional to avoid depending on existing binary files ?

[MarkBaker]

Again, I'm disinclined to use AbstractFunctional because it only really proves that we can read a file that we've generated ourselves, and not one generated by MS Excel or other external spreadsheet program. I think that as long as we keep the binaries small, and then they are justified for testing Readers

[PowerKiKi]

Fair enough, then it's good to merge for me.