Closed
Bug 686971
Opened 13 years ago
Closed 13 years ago
Leaving the See Also field empty or undefined while adding one using the Bug.update WebServices method no longer triggers 'that argument was not set'
Categories
(Bugzilla :: WebService, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 4.2
People
(Reporter: LpSolit, Assigned: timello)
References
Details
(Keywords: regression)
Attachments
(1 file)
344 bytes,
patch
|
LpSolit
:
review+
|
Details | Diff | Splinter Review |
webservice_bug_update.t expects to get '... input argument, and that argument was not set' as error message when leaving the See Also field empty or undefined while trying to add one to a bug using Bug.update. But in 4.2, we get 'is not a valid URL to a bug. See Also URLs should point to one of: ...'
Is this change expected? Or is it a failure in the validator to make sure that the value is set? I would expect that check_required_create_fields() would catch this.
Flags: blocking4.2+
Assignee | ||
Comment 1•13 years ago
|
||
That because we don't have a validator (ie.: _check_see_also) for see_also in Bug.pm... and Bugzilla::BugUrl->class_for is where it takes care of the validation. I think the point is more architectural than a problem. If we allow adding see also in Bug.update so I think we should add the validator and expect the same behavior of the others fields.
Assignee | ||
Comment 2•13 years ago
|
||
@mkanat │ LpSolit: Hmmm. Most empty fields return info that they are an empty field.
@mkanat │ LpSolit: I would think that the see also validation internally should perhaps do that.
@mkanat │ Unless it complicates the architecture.
Assignee: webservice → timello
Comment 3•13 years ago
|
||
Oh, you know, it does say "See Also" in the error message. I think that's enough. We can fix the test to expect the new error message, as long as the error code hasn't changed.
![]() |
Reporter | |
Comment 4•13 years ago
|
||
(In reply to Max Kanat-Alexander from comment #3)
> Oh, you know, it does say "See Also" in the error message. I think that's
> enough. We can fix the test to expect the new error message
I'm fine with fixing the tests, as long as someone can confirm that the current code works as expected, and that the new error message is indeed correct. If it appears that the error message is different because something is broken internally, then this is a blocker. Else this bug no longer blocks. mkanat/timello?
Assignee | ||
Comment 5•13 years ago
|
||
mkanat, as per your previous comment on IRC:
"@mkanat timello: I think ignoring empty values will probably make life easier for implementors."
So, here is that patch.
Attachment #577625 -
Flags: review?(LpSolit)
![]() |
Reporter | |
Comment 6•13 years ago
|
||
Comment on attachment 577625 [details] [diff] [review]
v1
>=== modified file 'Bugzilla/Bug.pm'
> $input = trim($input);
>
>+ return if !$input;
Nit: the whitespace between these two lines is useless.
r=LpSolit. I will fix Selenium scripts accordingly. Note that this change should be relnoted as this is an API change. We no longer throw an error but silently ignore such empty URLs.
Attachment #577625 -
Flags: review?(LpSolit) → review+
![]() |
Reporter | |
Updated•13 years ago
|
Assignee | ||
Comment 7•13 years ago
|
||
Committing to: bzr+ssh://timello%40gmail.com@bzr.mozilla.org/bugzilla/4.2/
modified Bugzilla/Bug.pm
Committed revision 7967.
Committing to: bzr+ssh://timello%40gmail.com@bzr.mozilla.org/bugzilla/trunk/
modified Bugzilla/Bug.pm
Committed revision 8019.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
![]() |
Reporter | |
Updated•13 years ago
|
Flags: testcase+
You need to log in
before you can comment on or make changes to this bug.
Description
•