Ever-present fields

Max Kanat-Alexander mkanat at bugzilla.org
Fri Oct 23 01:48:46 UTC 2009

On 10/22/2009 09:25 AM, Gervase Markham wrote:
> However, in
> the case of the following fields, which are configurable on/off in
> Bugzilla preferences, the API user would still have to check for
> existence before checking a value.

	Oh, actually, my current goal is to have parameters only control the
UI. They should only affect the backend when there is a really good
reason. So, for example, qa_contact would *always* be returned by the
WebService, even if it's disabled. This allows clients to have a totally
consistent API no matter how the administrator has configured the
system's parameters. It also greatly simplifies our implementation of
parameters (it generally limits them to controlling only templates).

> So my current plan is to only supply fields which have a value. This
> keeps data size down and avoids hardcoding "special" lists of fields.
> Let me know if you think this reasoning is wrong.

	Given the current direction of Bugzilla itself, I'd suggest that it
would be better to just always return the value of every field.

Competent, Friendly Bugzilla and Perl Services. Everything Else, too.

More information about the developers mailing list