Skip to content
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

Fixing #116, 'not' in strings. #117

Closed
wants to merge 1 commit into from
Closed

Conversation

kazie
Copy link

@kazie kazie commented Oct 31, 2017

This fix will clear the issue that I got when using "not" blocks for validation of string.

Example would be to add forbidden values (not enum) or anti-patterns (not pattern).

Implementation should be quite straight forwards, and be implementing "not" as a complete schema of its own - using the existing "NotSchema" class to validate the schema.

    This fix will clear the issue that I got when using "not" blocks for validation of string.
    Example would be to add forbidden values (not enum) or anti-patterns (not pattern).
    Implementation should be quite straight forwards, and be implementing "not" as a complete schema of its own - using the existing "NotSchema" class to validate the schema.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.2%) to 91.932% when pulling 96f25ee on kazie:notStringEval into d607795 on everit-org:master.

@erosb
Copy link
Contributor

erosb commented Oct 31, 2017

Thank you for your efforts, but I can't merge it. It is just a symptom of a deeper and more general problem. I added my explanation here: #116 (comment)

@erosb erosb closed this Oct 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants