JSON Schema can be used with most YAML documents resulting in a more portable and better documented solution than Rx or Kwalify. JSON Schema is the only of the three for which I have been able to find editor support. More information on using YAML and JSON Schema including tools and editor support is tracked … Read more
#!/bin/sh die () { echo >&2 “$@” exit 1 } [ “$#” -eq 1 ] || die “1 argument required, $# provided” echo $1 | grep -E -q ‘^[0-9]+$’ || die “Numeric argument required, $1 provided” while read dir do [ -d “$dir” ] || die “Directory $dir does not exist” rm -rf “$dir” done … Read more
If you are strictly using the HTTP authentication framework provided by RFC 7235 for your REST API, the correct HTTP code would actually be 401. From the RFC: The 401 (Unauthorized) status code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource. The server generating a … Read more
As per different sources, I think the minimum length in E-164 format depends on country to country. For eg: For Israel: The minimum phone number length (excluding the country code) is 8 digits. – Official Source (Country Code 972) For Sweden : The minimum number length (excluding the country code) is 7 digits. – Official … Read more
We had the same problem when making our API as well. We were looking for an HTTP status code equivalent to an InvalidArgumentException. After reading the source article below, we ended up using 422 Unprocessable Entity which states: The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity … Read more
Yes. Just as the error said, in HTML, attributes are #PCDATA meaning they’re parsed. This means you can use character entities in the attributes. Using & by itself is wrong and if not for lenient browsers and the fact that this is HTML not XHTML, would break the parsing. Just escape it as & and … Read more
Using the official java email package is the easiest: public static boolean isValidEmailAddress(String email) { boolean result = true; try { InternetAddress emailAddr = new InternetAddress(email); emailAddr.validate(); } catch (AddressException ex) { result = false; } return result; }
Each field constraint should be handled by a distinct validator annotation, or in other words it’s not suggested practice to have one field’s validation annotation checking against other fields; cross-field validation should be done at the class level. Additionally, the JSR-303 Section 2.2 preferred way to express multiple validations of the same type is via … Read more
in component: formData.form.controls[’email’].setErrors({‘incorrect’: true}); and in HTML: <input mdInput placeholder=”Email” type=”email” name=”email” required [(ngModel)]=”email” #email=”ngModel”> <div *ngIf=”!email.valid”>{{email.errors| json}}</div>
If “validation failure” means that there is some client error in the request, then use HTTP 400 (Bad Request). For instance if the URI is supposed to have an ISO-8601 date and you find that it’s in the wrong format or refers to February 31st, then you would return an HTTP 400. Ditto if you … Read more