From ef5893d023a6364999cb6dc27eee677cbe3e89ae Mon Sep 17 00:00:00 2001 From: ambujsingh Date: Wed, 27 May 2026 15:44:00 +0530 Subject: [PATCH] [rules score] use Markup_String for requirement description field Update `score_requirements_model.rsl` to change the `description` field type from `String` to `Markup_String`, enabling [[references]] in requirement descriptions to be rendered as Sphinx cross-refs. Required by: https://github.com/bmw-software-engineering/trlc/pull/192 --- .../rules/rules_score/trlc/config/score_requirements_model.rsl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bazel/rules/rules_score/trlc/config/score_requirements_model.rsl b/bazel/rules/rules_score/trlc/config/score_requirements_model.rsl index c0a7bee..523a372 100644 --- a/bazel/rules/rules_score/trlc/config/score_requirements_model.rsl +++ b/bazel/rules/rules_score/trlc/config/score_requirements_model.rsl @@ -29,7 +29,7 @@ enum Status { abstract type Requirement "Base type for all S-CORE requirements." { description "The normative requirement text. Must express an obligation (shall/should)." - String + Markup_String version "Monotonically increasing version counter. Increment on every content change." Integer note "Non-normative explanatory text providing additional context."