WMDE\Fundraising\Frontend\App\EventHandlers\OutputCookiePreference

Complexity

Total Complexity

3

Size/Duplication

Total Lines	20
Duplicated Lines	0 %

Importance

Changes	1
Bugs	0	Features	0

2 Methods

Rating	Name	Duplication	Size	Complexity
A	getSubscribedEvents()	0	3	1
A	addCookiePreference()	0	12	2

<?php

declare( strict_types = 1 );

namespace WMDE\Fundraising\Frontend\App\EventHandlers;

use Symfony\Component\EventDispatcher\EventSubscriberInterface;
use Symfony\Component\HttpKernel\Event\FilterResponseEvent;
use Symfony\Component\HttpKernel\KernelEvents;

/**
 * Modify all HTML responses, adding the current consent state as a data attribute.
 *
 * This helps us keeping the consent cookie HTTP-only.
 *
 * Manipulating the HTML output directly, relying on an existing attribute, is
 * brittle, but until we have a better way for rendering our application shell
 * (see https://phabricator.wikimedia.org/T248460 ), this will have to do.
 */
class OutputCookiePreference implements EventSubscriberInterface {

	public static function getSubscribedEvents() {
		return [
			KernelEvents::RESPONSE => [ 'addCookiePreference' ]
		];
	}

	public function addCookiePreference( FilterResponseEvent $event ): void {
		if ( !$event->isMasterRequest() ) {
			return;
		}

		$cookieConsent = $event->getRequest()->cookies->get( 'cookie_consent', 'unset' );
		$response = $event->getResponse();

		$response->setContent( str_replace(
			'data-application-vars=',
			'data-cookie-consent="' . $cookieConsent . '" data-application-vars=',
			$response->getContent()
		) );
	}
}