Next

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?