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 status-bydesign
Search options not deleted
user 2
Indicates that a submitted issue is actually due to the existing design of the system and is not considered erroneous behaviour.
2
votes
1
vote
Accepted
Post body is optional field in questions method?
If you set body to false in the request, body on all the responses (two different fields of two different types in two different contexts with the same name... makes it hard to discuss...) is not set. …
- 18.7k
1
vote
Are these fields redundant?
At this phase, this is technically correct. Note that changes in the main site could break this assumption over the lifetime of v1 of the API (not to imply any such changes are in the pipeline - or e …
- 18.7k
3
votes
Accepted
1
vote
Server has stopped obeying Accept-encoding header
A 406 response breaks* a ton of proxies. In effect, if we strictly follow the standard we prevent many people on corporate networks from accessing the API.
We found this out the hard way.
*Technic …
- 18.7k
3
votes
redundant data in users
These are around because of popular demand in the private beta.
I have mixed feelings about them, honestly.
However, I'd rather not remove anything this late in the beta.
- 18.7k
1
vote
nottagged parameter not documented
No it doesn't. For that matter, I don't recall /questions ever taking nottagged.
The API just doesn't reject URLs with extraneous parameters.
http://api.stackoverflow.com/1.0/stats?unicorns=yes+ple …
- 18.7k
1
vote
Accepted
api.meta.stackoverflow.com has state:normal - is this correct
StackOverflow Meta is different for the other Metas.
This is one of the reasons that meta status is indicated with state and not just the site_url.
Valid states are:
normal - a full member of the …
- 18.7k
0
votes
On Stackauth /sites new meta sites have wrong name
Infer meta relationships based on the site_url, not name.
The differences in naming scheme are intentional.
- 18.7k
2
votes
Accepted
Badges displayed incorrectly?
stackexchange.com user ids are not the same as stackoverflow.com user ids (are not the same as Server Fault's, Super User's, etc., etc.).
Stack Overflow user 1719 is voyce, who has the five badges th …
- 18.7k
2
votes
Accepted
api.money.stackexchange.com returning questions from 2009?
No, money.stackexchange is the first site seeded with the content of an older, SE 1.0 site. Accordingly, some of the content is "older" than the site itself, as are some of its users.
In this case, …
- 18.7k
3
votes
Accepted
Method /users/{id} doesn't return "about_me" if the user has never modified it
There are a great many fields on objects returned by the API that will be omitted if they are not set.
The user fields you mentioned.
locked_date, bounty_date, etc. on questions and answers
a whole …
- 18.7k
1
vote
Accepted
Inconsistent sort ordering on users?
Sorts are not guaranteed to be stable. Check the creation_date on each user to convince yourself they are in order.
- 18.7k
3
votes
Accepted
Question's title attribute is not HTML encoded
Question titles aren't markdown, they're plain text.
Accordingly, if you're going to display them in HTML you shouldn't display them "raw".
- 18.7k
0
votes
What happened to nothingtoinstall.com?
NothingToInstall has been rolled back to WebApps.StackExchange. This has been discussed elsewhere, and should continue to be discussed elsewhere (read: no debate on StackApps, take it to the appropri …
- 18.7k