add follow-up fetching to CR API
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	hashar
	Jul 15 2011, 10:21 PM

Description

The CodeReview API does not let us fetch follow up for a given set of revisions.

This could be made an option when querying for list=coderevisions. Each <revision> could contains more <revisions> elements.

An option could be added to handle this recursively. Possible traps:

revisions might appear more than one time, we want to avoid sending the same metadata over and over.
avoid loops!! :b

Version: unspecified
Severity: enhancement

		Status	Subtype	Assigned	Task
		Declined	Feature	None	T28416 Ability to view the revision follow-up tree
		Resolved		None	T31916 add follow-up fetching to CR API

• bzimport raised the priority of this task from to Needs Triage.Nov 21 2014, 11:31 PM

• bzimport set Reference to bz29916.

• bzimport added a subscriber: Unknown Object (MLST).

I'd avoid recursion here; easiest and safest to only show one level. :)

(In reply to comment #1)

I'd avoid recursion here; easiest and safest to only show one level. :)

Indeed. Although unlikely (these aren't Wikipedia categories!!), I think doing 1 level makes sense

I'm guessing 1 level is just all the followup revisions for the passed numbers (not any followups to those)?

Also, what level of information do you want returning for the followups? Same as the GUI? More? Less?

Well it can be customized for list=coderevisions using crprop.

By default revid|status|author|timestamp I guess.

Done in r96321