Problem/Motivation

Mailhandler uses default analyzer result for its analyzer collaboration by directly specifying the object and the topic.

Proposed resolution

Since DefaultAnalyzerResult is in Inmail core, we should remove unnecessary part: DefaultAnalyzerResult::TOPIC from our calls $processor_result->getAnalyzerResult().

Remaining tasks

User interface changes

API changes

Data model changes

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mbovan created an issue. See original summary.

toncic’s picture

Assigned: Unassigned » toncic
Status: Active » Needs review
FileSize
10.7 KB

Remove DefaultAnalyzerResult from call getAnalyzerResult(). Test is failing becaus HEAD fails.

Status: Needs review » Needs work

The last submitted patch, 2: remove_default_analyzer-2816131-2.patch, failed testing.

The last submitted patch, 2: remove_default_analyzer-2816131-2.patch, failed testing.

toncic’s picture

Trying again the same patch when HEAD is fixed.

mbovan’s picture

Status: Needs review » Needs work

PHPStorm is complaining about needed parameter in getAnalyzerResult(). Seems like a bug in ProcessorResultInterface. Could you open an issue in Inmail for that.

Also, we have many unnecessary calls to ensureAnalyzerResult() (after the related Inmail change was introduced). We can remove them as well.

toncic’s picture

Removed ensureAnalyzerResult.
Created issue in inmail.

  • mbovan committed 4efdf41 on 8.x-1.x authored by toncic92
    Issue #2816131 by toncic92: Remove default analyzer topic call
    
mbovan’s picture

Status: Needs review » Fixed

Very nice! Thank you!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.