IHasTranslationImports exported incorrectly

Bug #668194 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Undecided
Jeroen T. Vermeulen

Bug Description

The IHasTranslationImports classes implement IHasTranslationImports, which is exported on the API. Unfortunately doing it this way turns out to create a separate API class (unreachable as far as I can see) called object_with_translation_imports instead of adding the interface's methods to person, distroseries etc. The test infrastructure was hiding this fact by making it look as if things worked the way we wanted (bug 668190) once we started exporting a method on this interface (bug 664327).

Instead of making Person, Product etc. implement IHasTranslationImports we need to derive IPerson, IProduct etc. from IHasTranslationImports. Doing that will upset our module dependencies a bit, so it looks like there will be circular imports.

Related branches

summary: - IHasTranslationImports.getTranslationImportQueueEntries exported wrongly
+ IHasTranslationImports exported incorrectly
Changed in rosetta:
status: In Progress → Fix Committed
tags: added: qa-needstesting
Revision history for this message
Launchpad QA Bot (lpqabot) wrote : Bug fixed by a commit
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-ok
removed: qa-needstesting
Changed in rosetta:
status: Fix Committed → Fix Released
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.