-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Fix a xfaFaxtory
typo in the shadowing in the PDFDocument.xfaFactory
getter, and some other clean-up
#14152
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
Conversation
…ry` getter With this typo the shadowing doesn't actually work, which causes these checks to be unnecessarily repeated. In this particular case it didn't have a significant performance impact, however we should definately fix this nonetheless.
In these cases there's no good reason, in my opinion, to duplicate the `shadow`-lines since that unnecessarily increases the risk of simple typos (see the previous patch).
Also (slightly) simplifies a couple of small getters/methods related to the `XFAFactory`-instance.
…for consistency All other similar getters are called `numPages` throughout the code-base, and improved consistency should always be a good thing.
/botio xfatest |
From: Bot.io (Linux m4)ReceivedCommand cmd_xfatest from @timvandermeij received. Current queue size: 0 Live output at: http://54.241.84.105:8877/d9dbb4fdd40cb60/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_xfatest from @timvandermeij received. Current queue size: 1 Live output at: http://54.193.163.58:8877/144faa16643f60a/output.txt |
From: Bot.io (Linux m4)FailedFull output at http://54.241.84.105:8877/d9dbb4fdd40cb60/output.txt Total script time: 9.44 mins
Image differences available at: http://54.241.84.105:8877/d9dbb4fdd40cb60/reftest-analyzer.html#web=eq.log |
From: Bot.io (Windows)FailedFull output at http://54.193.163.58:8877/144faa16643f60a/output.txt Total script time: 14.21 mins
Image differences available at: http://54.193.163.58:8877/144faa16643f60a/reftest-analyzer.html#web=eq.log |
Nice find; thank you for fixing this! |
Please refer to the individual commit messages for additional details.