issues
search
tobyink
/
p5-json-schema
1
stars
4
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Feature request - Strict mode
#20
tobyink
opened
3 years ago
1
Number should accept exponential form as per JSON schema specification
#19
tobyink
opened
3 years ago
2
keyword "required" not used like documented
#18
tobyink
opened
3 years ago
3
Useless use of concatenation (.) or string in void context
#17
tobyink
opened
3 years ago
3
JSON::Schema can't validate the core schema against itself
#16
tobyink
opened
3 years ago
1
dead condition is used. Boolean never be detected
#15
tobyink
opened
3 years ago
0
Format date-time Regex does not Match Timezone Offset and Fractions of a Second
#14
tobyink
opened
3 years ago
0
Small error in POD
#13
tobyink
opened
3 years ago
0
remove use of convert_blessed_universally
#12
tobyink
opened
3 years ago
0
scientific notation on numbers don't validate as numbers
#11
tobyink
opened
3 years ago
1
Running regex changes behavior of validation
#10
tobyink
opened
3 years ago
0
Error property keys have a $. prefix
#9
chandywerks
opened
8 years ago
0
Fixed email regex
#8
Relequestual
opened
9 years ago
1
Email regex validation is incorrect
#7
Relequestual
opened
9 years ago
0
$ref support example?
#6
Relequestual
opened
9 years ago
0
keyword "required" not used like documented in latest json schema
#5
nicolasfranck
closed
9 years ago
8
Fix miss places )'s causing warnings about string concatination in void context.
#4
amishHammer
opened
10 years ago
0
should remove 'no autovivification' pragma from JSON::Schema::Helper
#3
matthof
opened
10 years ago
0
convert_blessed_universally flag in JSON::Schema::Helper is leaky
#2
matthof
opened
10 years ago
3
Remove detect() method and drop HTTP::Link::Parser dependency?
#1
matthof
opened
10 years ago
1