As a developer, I would like to have one activity interpreter per type of entity

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: 6.2.0 CE M5
• Fix Version/s: 6.2.0 CE M5
• Component/s: Social Networking, Social Networking > Activities
• Labels: None
• Epic/Theme:
  • Social_WCM
• Similar Issues: Show 5 results ; ;

  LPS-34481	As a developer I would like to have more consistent language keys for activities
  LPS-21949	service builder : 'per entity building'
  LPS-34295	As a developer I would like to handle all the export/import related path methods in one place
  LPS-39440	As a test developer I would like the test listeners to be registered automatically by annotations
  LPS-45996	As a developer, I would like to have just one method on the portlet controller to create or update Kaleo Draft Definitions

By adding trash activities on folders of entities, some of the current activity interpreters handle multiple classes (i.e. the entity and its folder class). We should split these interpreters and rename them based on the class they handle.

For example:

BookmarksActivityInterpreter -> BookmarksEntryActivityInterpreter and BookmarksFolderActivityInterpreter