Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
4,925
edits
No edit summary |
|||
| Line 64: | Line 64: | ||
== Field Control == | == Field Control == | ||
NOT IMPLEMENTED YET | |||
Each call returns a number of fields by default. Often, it's all available fields, but for some calls (e.g. searches, individual bugs) it's fewer than that. You can control exactly what fields you get using the '''include_field''' and '''exclude_field''' parameters. These take a comma-separated list of field names, and work as follows: | Each call returns a number of fields by default. Often, it's all available fields, but for some calls (e.g. searches, individual bugs) it's fewer than that. You can control exactly what fields you get using the '''include_field''' and '''exclude_field''' parameters. These take a comma-separated list of field names, and work as follows: | ||
* If you specify some include_fields, you select just those fields | * If you specify some include_fields, you select just those fields | ||
* If one of your field names is "_default" (note underscore), you select the default fields plus | * If one of your field names is "_default" (note underscore), you select the default fields plus any others you specify | ||
* If one of your field names is "_all" (note underscore), you select all available fields, regardless of whether you specify any others as well | * If one of your field names is "_all" (note underscore), you select all available fields, regardless of whether you specify any others as well | ||
* After that, if you have specified exclude_fields, they are removed before the data is returned. | * After that, if you have specified exclude_fields, they are removed before the data is returned. | ||