From 6ebb173c50f6b8d82981381a6d757bf6c6c7d620 Mon Sep 17 00:00:00 2001 From: Patrick Lucas Date: Fri, 13 Mar 2026 09:50:05 +0100 Subject: [PATCH] Do not require explicit scenario definitions Users are encouraged to explicitly define scenarios in the repository/scenarios section, but this is not required. Scenarios can be used implicitly by name without an explicit definition. This commit also corrects two minor documentation errors. Fixes #283 --- .../src/main/resources/xsd/repository.xsd | 24 ++----------------- 1 file changed, 2 insertions(+), 22 deletions(-) diff --git a/repository/src/main/resources/xsd/repository.xsd b/repository/src/main/resources/xsd/repository.xsd index e94c6bc..d6683a8 100644 --- a/repository/src/main/resources/xsd/repository.xsd +++ b/repository/src/main/resources/xsd/repository.xsd @@ -195,7 +195,7 @@ - Combination of message id and scenario ID must be unique + Combination of message id and scenario must be unique @@ -260,31 +260,11 @@ - - - - - - - - - - - - - - - - - - - - - The default scenario is id='1' name='base'. + The default scenario is name='base'.