Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with schema
Search options not deleted
user 34752
3
votes
1
answer
177
views
What's best for a client library: userland code or schema files?
There are a number of popular client libraries that use this kind of schema pattern, but I'm trying to weigh up its positives and negatives. … OpenStack APIs seem to be also moving towards json-schema.
Are there any strong reasons why relying on schemas is a bad idea for a client library, and/or why userland code is a better approach? …
- 233