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 api-design
Search options not deleted
user 33790
Application Programming Interface (API) Design discusses best practises for creating libraries intended for general purpose or public use.
3
votes
Accepted
How to handle URIs containing parameters not used by the API?
I would argue that your current approach is the one that follows the principle of least astonishment.
RESTfully-speaking, you defined two different resources under v1: js and es6. There’s no reason …
- 644