[
https://issues.apache.org/jira/browse/UNOMI-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-1032:
-------------------------------
Fix Version/s: unomi-tracker-2.1.0
> Tracker: modernize the code base, with tests that prove existing websites are
> not affected
> ------------------------------------------------------------------------------------------
>
> Key: UNOMI-1032
> URL: https://issues.apache.org/jira/browse/UNOMI-1032
> Project: Apache Unomi
> Issue Type: Improvement
> Components: unomi-tracker
> Reporter: Serge Huber
> Priority: Major
> Fix For: unomi-tracker-2.1.0
>
>
> The tracker is a single 1,600-line JavaScript file built with old tools,
> which makes it hard to maintain and keeps security warnings open. We want to
> update the tools, split the code into modules and move it to TypeScript,
> without changing anything for the websites that use it. Before changing the
> code, we need tests that show the tracker behaves exactly as before.
> Steps, in this order (one sub-task each):
> # Compatibility test harness
> # Upgrade the build tools (rollup 4, ESLint 9 or later)
> # Split the source into modules
> # Convert to TypeScript
> Each step is merged only when the harness shows no difference other than the
> ones it lists on purpose.
> Planned after the tracker 2.0.0 release.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
