Tagged Questions
2
votes
1answer
65 views
API Help Suggestion: include range [1, 100] on pagesize
I see that range is being used to indicate valid range on most numeric parameters
e.g.
32-bit integer, range [0, 2,147,483,647]
32-bit integer, range [1, 2,147,483,647]
The valid range for ...
1
vote
1answer
61 views
API Help Suggestion: /users/{id}/badges id parameter clarification
On /users/{id}/badges, the description of id parameter diverges from the inferred standard.
e.g.
a semicolon delimited list of user ids
vs
A single primary key identifier or a vectorized, ...
0
votes
1answer
70 views
help page suggestion: /questions/tagged/{tags} - tags param clarification
Method removed
it is not clear what a 'list' of tags looks like.
does this parameter follow the semicolon seperated list format of the id param?
is it a comma separated list?
2
votes
1answer
87 views
help page suggestion: indication of integral values vs real numbers
number is an very ambiguous term.
It would be helpful if there was an indication of values that can return as non-integral.
In a javascript context this is not an issue, but most devs, myself ...
1
vote
1answer
54 views
help page suggestion: json results for help pages
it would simplify machine reading if we could apply type=jsontext to api-help pages, including the index.
update
...
1
vote
1answer
65 views
help page suggestion: position required parameters at top
in the case of id, it is now placed at the bottom of the page.
It makes sense to place required parameters at the top of the page with a slight separation, perhaps an <hr> or an icon.
1
vote
1answer
51 views
help page suggestion: exemplars - working example urls for each route
It would take a lot of the guess work out of sussing the api if each route's page provided a small handful of working urls.
This would also serve to provide an authoritative result exemplar.
