The functionality that verifies and records a view for a boost (and then triggers lifecycle events) is hidden away inside v2/analytics/views api controller alongside the functionality for recording entity/activity views. This boost functionality needs to be extracted and implemented within Core\Boost namespace with either a common View interface or extending a View abstract and then implement the concrete boost view functionality.

added scoped label

changed weight to 3

assigned to @gthouret

added scoped label

added scoped label

added scoped label

changed the description

changed time estimate to 4h

added scoped label and automatically removed label

Are we still planning on storing in the views table?

added scoped label and automatically removed label

removed label

added to epic &103

added scoped label and automatically removed label

added scoped label

added scoped label

removed label

added scoped label

added 1h of time spent at 2019-12-03

mentioned in commit 3200ea77

Pushed branch with an incompatible name so pipelines failed. Renamed to extract-view-api-1077

Just need to attempt to add Spec test for the Views if that is possible -singleton usage of Core\Analytics\App::_() might make spec test not possible.