further improvements to API collection page ids

Bug #627027 reported by Robert Collins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Bug 606184 makes page ids for collections significantly better, in that there is a rough domain-indicator on them.

I'd like us to take this further though, and get to the point that instead of
ScopedCollection:CollectionResource:#bug-attachment-resource
we see
IBug:attachments

Now, I know that for /bugs/xxx/attachments, its actually a noddy example - humans can categorise and group this very quickly, but this isn't true for all APIs, nor is it true for people getting up to speed, and its not the case for computerised analysis either.

The use cases are 'looking at the page ID for a collection an engineer can determine the code to look at accurately and promptly', and 'oopses can reliably group all failures for a page id as the first-key in the grouping clause'.

The current (improved) page id's don't meet either of these criteria: multiple types can export a collection of a particular interface, and even a single type can export multiple collections of a particular interface, each collection possibly running very different code.

Revision history for this message
Gary Poster (gary) wrote :

We believe that this is a reasonable theoretical concern, but not a practical one at this time. Moreover, the (reasonable theoretical) concern is an apt description of the entire page id generation story, so we ought to consider the whole page id when we consider addressing this kind of issue, not just this particular part.

Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.