From 9c745453ba10c0b48b688818717f9a6c53ee36fa Mon Sep 17 00:00:00 2001 From: Plamen Boychev Date: Wed, 15 Jan 2025 10:05:01 +0200 Subject: [PATCH] docs: Release notes updated with the fix details. --- docs/versions/latest/Release.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/versions/latest/Release.md b/docs/versions/latest/Release.md index 5fb13d07c..6d003669c 100644 --- a/docs/versions/latest/Release.md +++ b/docs/versions/latest/Release.md @@ -122,4 +122,17 @@ The question is updated: ## Upgrade procedure +### *Dynamic type definitions for the unit tests framework.* + +The package name and version of the type definitions are being installed dynamically based on the configuration of the solution. +This ensures the type definitions available for type hinting / autocomplete in the IDE and for the transpilation are matching the actual code definitions of the unit test framework. + +#### Previous Behavior + +The type definitions installed were always the same package and version - the [BTVA built-in Jasmine definitions](https://github.com/vmware/build-tools-for-vmware-aria/tree/v3.1.1/vro-types/jasmine) (link is to v3.1.1, might be outdated at later point in time). + +#### New Behavior + +The configuration in the pom file affects both the framework being used and its type definitions being made available. + [//]: # (Explain in details if something needs to be done)