akira/pdfjs-dist - pdfjs-dist - Gitea: Git with a cup of tea

Tree: 00d67371ec

Author	SHA1	Message	Date
Tim van der Meij	35730148a7	Convert the files in the `/test/unit` folder to ES6 modules	8 years ago
porlan1	d9e1cb7955	unit test files as UMD modules	8 years ago
Jonas Jenwald	c850968fa7	Remove `globals` that are now unnecessary thanks to the use of various ESLint environments (e.g. Node, ShellJS, Jasmine)	8 years ago
Jonas Jenwald	2f3805efbc	Switch to using ESLint, instead of JSHint, for linting Please note that most of the necessary code adjustments were made in PR 7890. ESLint has a number of advantageous properties, compared to JSHint. Among those are: - The ability to find subtle bugs, thanks to more rules (e.g. PR 7881). - Much more customizable in general, and many rules allow fine-tuned behaviour rather than the just the on/off rules in JSHint. - Many more rules that can help developers avoid bugs, and a lot of rules that can be used to enforce a consistent coding style. The latter should be particularily useful for new contributors (and reduce the amount of stylistic review comments necessary). - The ability to easily specify exactly what rules to use/not to use, as opposed to JSHint which has a default set. Note: in future JSHint version some of the rules we depend on will be removed, according to warnings in http://jshint.com/docs/options/, so we wouldn't be able to update without losing lint coverage. - More easily disable one, or more, rules temporarily. In JSHint this requires using a numeric code, which isn't very user friendly, whereas in ESLint the rule name is simply used instead. By default there's no rules enabled in ESLint, but there are some default rule sets available. However, to prevent linting failures if we update ESLint in the future, it seemed easier to just explicitly specify what rules we want. Obviously this makes the ESLint config file somewhat bigger than the old JSHint config file, but given how rarely that one has been updated over the years I don't think that matters too much. I've tried, to the best of my ability, to ensure that we enable the same rules for ESLint that we had for JSHint. Furthermore, I've also enabled a number of rules that seemed to make sense, both to catch possible errors and various style guide violations. Despite the ESLint README claiming that it's slower that JSHint, https://github.com/eslint/eslint#how-does-eslint-performance-compare-to-jshint, locally this patch actually reduces the runtime for `gulp` lint (by approximately 20-25%). A couple of stylistic rules that would have been nice to enable, but where our code currently differs to much to make it feasible: - `comma-dangle`, controls trailing commas in Objects and Arrays (among others). - `object-curly-spacing`, controls spacing inside of Objects. - `spaced-comment`, used to enforce spaces after `//` and `/*. (This is made difficult by the fact that there's still some usage of the old preprocessor left.) Rules that I indend to look into possibly enabling in follow-ups, if it seems to make sense: `no-else-return`, `no-lonely-if`, `brace-style` with the `allowSingleLine` parameter removed. Useful links: - http://eslint.org/docs/user-guide/configuring - http://eslint.org/docs/rules/	8 years ago
Jonas Jenwald	ad915f8af1	Fix errors reported by the `comma-spacing` ESLint rule http://eslint.org/docs/rules/comma-spacing	8 years ago
Tim van der Meij	5194e68134	Lint: correct code style violations Manual observations and working with other linting tools found these.	9 years ago
Jonas Jenwald	4523ae0b91	Add a couple of `CipherTransformFactory` unit-tests to check that blank passwords are correctly rejected	9 years ago
Jonas Jenwald	b0ce83b372	Use `beforeAll`/`afterAll` in `CipherTransformFactory` in crypto_spec.js (issue 6905 This patch also adds/improves utility functions for checking if the passwords are correct/incorrect, and replaces `string2binary` with `stringToBytes`. Finally the patch does away with the `DictMock`, in favour of using actual `Dict`s. Re: issue 6905.	9 years ago
Yury Delendik	0a700fa29d	Updates Jasmine version.	9 years ago
Manas	a2ba1b8189	Uses editorconfig to maintain consistent coding styles Removes the following as they unnecessary /* -- Mode: Java; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -- / / vim: set shiftwidth=2 tabstop=2 autoindent cindent expandtab: */	10 years ago
Jonas Jenwald	f59e20226c	Slightly improved Crypto unit tests Currently in the tests which check that incorrect passwords are rejected, we don't ensure that the exceptions thrown are the ones we expect. This patch improves the current situation, so that we actually can be sure that the code "fails" in the correct way. Note: This patch also fixes some cases of weird indentation in the file.	10 years ago
Tim van der Meij	34728ee49b	Removing unused code	11 years ago
Daniel West	1fce2856c6	Added support for decrypting PDF 1.7/2.0 Algorithm 5 revision 5 and 6. Added AES128 Encryption Added AES258 Encryption/Decryption Added SHA256 Added SHA512 Added class to handle 8 byte integers and associated bit operations Added SHA384 *Added routines to handle new algorithm and perform PDF2.0 hashing.	11 years ago
Jonas Jenwald	9e3f7e4d6d	Fix coding style in test/unit/crypto_spec.js	11 years ago
Nicholas Nethercote	fdb7c218da	Use a cache to minimize the number of Name objects.	11 years ago
Yury Delendik	81f8f92696	Adds web/* and test/* for jshint target	12 years ago
Yury Delendik	910ba0b91f	Fixes user and owner passwords logic	13 years ago
notmasteryet	50a16573ad	Add unit tests for calculateMD5, ARCFourCipher, and PredictorStream	13 years ago