summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix type hint of schemas, for example for Required('key') (#478)HEADmasterDS/Charlie2023-02-221-16/+20
|
* Set static PyPI project description (#476)Philip Allgaier2023-02-131-2/+1
|
* add typing information (#475)DS/Charlie2023-02-1310-105/+147
|
* Change to SPDX conform license string (#472)elprimato2022-10-231-1/+1
| | | Co-authored-by: Volker Schaus <volker.schaus@esa.int>
* Fix a few typos (#470)Tim Gates2022-07-133-5/+5
|
* Release 0.13.1 (#469)0.13.1Philip Allgaier2022-04-073-3/+19
|
* Add tests for `Object` and `MultipleInvalid` (#467)Philip Allgaier2022-04-032-13/+45
|
* Style and warning cleanups in README (#466)Philip Allgaier2022-04-031-50/+18
|
* Extend README to include coverage run commands + unpin `setupstools` (#465)Philip Allgaier2022-04-032-3/+7
|
* `pytest` migration + enable Python 3.10 (#464)Philip Allgaier2022-04-036-227/+203
| | | | Co-authored-by: pgajdos <pgajdos@suse.cz> Co-authored-by: epenet <epenet@users.noreply.github.com>
* Convert codebase to adhere to flake8 W504 (PEP 8) (#462)Philip Allgaier2022-04-024-17/+18
|
* Enable flake8 in github actions (#459)epenet2022-04-025-22/+26
|
* Ignore `Enum` if it is unavailable (#454)epenet2022-04-023-33/+42
|
* Enable github actions (#457)epenet2022-04-022-0/+39
|
* Fix email regex match for Python 2.7 (#456)epenet2022-04-012-3/+23
|
* Release 0.13.00.13.0Philip Allgaier2022-03-302-1/+7
|
* Display valid Enum values in Coerceepenet2022-03-112-0/+40
|
* Release 0.12.2v0.12.20.12.2Adam Tankanow2021-09-212-2/+8
|
* Change email regex match to fullmatchleonidguadalupe2021-08-311-1/+1
| | | | | | | | | This PR is about the current method used to conditionally match user and domain regex to email. currently, it's using match which wrongfully accepts entries if domain has special characters after .com it currently accepts, john@voluptuous.com> or john!@voluptuous.org!@($*! thus, we need to fullmatch the domain or user to avoid such entries and validate them properly.
* ISSUE-439: Fix broken testAdam Tankanow2021-02-201-2/+2
|
* Revert "Ensure `Maybe` propagates error information (#411)"Adam Tankanow2021-02-202-2/+2
| | | | This reverts commit da3cc967f7b16f18bf8c1feacfeced8f10ce9e40.
* Include the regular expression in the error messagetimski2021-01-281-2/+2
|
* Release 0.12.10.12.1Philip Allgaier2020-12-062-2/+19
|
* Extend tests for `Schema` with empty list or dict (#438)Philip Allgaier2020-12-061-16/+47
|
* Remove value enumeration when validating empty list (#434)monopolis2020-12-063-3/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | * Add ability to use custom flags when running tox .. so that you can e.g. run `tox -- --pdb` to get a debugger on test failures. * Remove value enumeration when validating empty list (#397) The behaviour seems to have been introduced in commit 95489bd443e9a654 that modified the schema of an empty list in order to provide a consistent behaviour between Schema({}) and Schema([]). The commit introduced an enumeration of the incorrect values rather than the expected behaviour of showing the key with the incorrect value. This commit provides the expected behaviour, and is also consistent with the 'pathless' behaviour currently implemented, meaning that - Schema([])([1]) -> 'not a valid value @ data[1]' - Schema({'key': []})({'key': [1]) -> 'not a valid dictionary value @ data['key']. Finally, as new unit test is provided to ensure that the new behaviour remains intact.
* Grouped `Maybe` tests plus added a `Range` test (#437)Philip Allgaier2020-12-062-17/+25
|
* Ensure `Maybe` propagates error information (#411)monopolis2020-12-062-2/+18
| | | | | | | | | | Due to Any evaluating all options, and raising the exception from the first encountered error, Maybe would discard the expected error raised by the provided validator and only raise a invalid value error (due to values not being None). This commit changes the order of the validators in Maybe so that the first evaluated error, and thus returned is that of the provided validator.
* Enable stable travis-ci python 3.9 buildPhilip Allgaier2020-11-191-1/+1
|
* Add sorted() for In and NotIn + fix tests (#436)Philip Allgaier2020-11-182-6/+6
|
* Improve error message for In() and NotIn() (#425)vmaillol-altair2020-11-181-2/+4
| | | | | * Update validators.py * Update In and NotIn validator error message
* Extended a few tests (#435)Philip Allgaier2020-11-181-33/+35
|
* Use "py3.9-dev" in travis-ci for nowPhilip Allgaier2020-10-071-1/+1
| | | The python 3.9 binary from travis-ci is not yet available although Python 3.9 itself has been officially released.
* Add Python 3.9 support (#433)Philip Allgaier2020-10-073-1/+3
|
* Fixed typos + made spelling more consistent (#431)Philip Allgaier2020-09-224-78/+78
| | | | | * Fixed typos + made spelling more consistent * Adjustments
* Update changelog for 0.12.0Philip Allgaier2020-09-211-1/+14
|
* Newer coverage version required for python-3.8Philip Allgaier2020-09-211-1/+1
|
* Cleanup python versions (remove unsupported + add 3.8)Philip Allgaier2020-09-213-19/+3
|
* Updated README to include shields from pypiPhilip Allgaier2020-09-211-0/+3
|
* Fix most important flake8 errors/warningsPhilip Allgaier2020-09-213-19/+25
|
* Added additional tests for Range, Clamp and Length + catch exceptions (#427)Philip Allgaier2020-09-202-16/+101
|
* Update README.mdAlec Thomas2020-08-241-1/+1
|
* Fixed issue with 'required' not being set properly and added test (#420)EarQuack2020-04-012-0/+9
| | | A fix for issue #419 - schema required flag isn't set properly in all cases
* Update issue templatesAlec Thomas2020-01-211-0/+16
|
* Switch to CONTRIBUTIONS ONLYAlec Thomas2020-01-211-0/+9
|
* Update schema_builder.pyTim Gates2019-12-061-1/+1
|
* Fix simple typo: arugment -> argumentTim Gates2019-12-061-1/+1
| | | | Closes #415
* Handle incomparable values in Range (#414)monopolis2019-11-282-17/+37
| | | | | | | | | | In Python3 some values that are comparable in Python2 are no longer comparable. One instance of this is None, which in Python2 is always less than any other object. In Python3, however, a TypeError is raised if it is used in a comparison. This commit handles said TypeError and issues a RangeInvalid exception instead.
* Allow a discrminant field in validators (#368)Yashvardhan Didwania2019-08-152-1/+76
|
* 0.11.7 including changelog.Alec Thomas2019-08-132-2/+2
|
* Updated changelog with latest changes since release of 0.11.5Simeon Visser2019-08-131-0/+18
|