danielsiepmann/tracking
danielsiepmann/tracking
1
0
mirror of https://github.com/DanielSiepmann/tracking.git synced 2024-11-14 18:46:10 +01:00
Code Issues Releases Wiki Activity
tracking/readme.rst
Daniel Siepmann d3878d928d Improve CI 
* Adjust names of tasks.
* Add composer require checker.
* Install without plugins to not use custom installer and stay
  compatible with require checker.
* Stay phpunit 10 compatible.
2020-04-07 15:32:29 +02:00

2.1 KiB
Raw Blame History

About

This extension should only demonstrate technical features of TYPO3. It is not intended for use in production systems.

The following features should be demonstrated:

PSR-4 Autoloading Standard

Use composer.json to provide autoloading information. Classes will be loaded when needed. No need for require statements.

PSR-12 Extended Coding Style Guide

Current stable Coding Style Guide, applied via Coding Sniffer.

PSR-7 HTTP Message Interface

Also known as Request Response, used to create tracking information from incoming request.

PSR-11 Container Interface

Also known as Dependency Injection. Used to resolve external dependencies, e.g. foreign classes. Existing TYPO3 factories are used to build QueryBuilder instances. Also DI is "misused" to provide configuration for dashboard widgets and tracking blacklists.

PSR-15 HTTP Handlers

Also known as middlewares. Used to hook into processing to create tracking information.

PSR-14 Event Dispatcher

Not in use yet.

EXT:dashboard

Used to visualize collected tracking information.

Todos

  1. Add 100% code coverage (Widgets are missing)
  2. Add version matrix to test with multiple PHP versions.
  3. Add campaigns if possible (twitter parameter, etc.)
  4. Add referrer if available.
  5. Add operating System
    1. Another Symfony Expression which returns the OS ("Ubuntu", "Macintosh", "Android", "iPhone", "Windows")
  6. Add further widgets.
    1. Grouped by user agents (bar).
    2. Top 404 requests (Collect them to show them, doughnut).
  7. Move bot detection to another rule.
    1. Keep indexing those requests, but mark them as bot and separate them in widgets.
    2. Provide an overview of crawls as widgets. E.g. to allow fine grained robots.txt.
  8. Add information to Admin Panel.
  9. Add command that will iterate over all DB entries and remove ones matching the black list rule. E.g. if rule is adjusted in meanwhile.

Example

The following widgets are added and could look like:

image

A new record is added which looks like:

image