There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
CommonPartHandler.ContentTypeWithACommonPart() could use content type definition from context
Instead of fetching the content type definition from the ContentDefinitionManager instance for checking whether CommonPart is attached to the current type or not it could use the definition already loaded in the ActivatingContentContext object. Not sure
if the current implementation causes any overhead, but it's a needless call anyway.