opsx-gherkin 2.0.0 → 2.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,10 @@
|
|
|
1
|
+
## [2.0.1](https://github.com/aquine-kujaruk/opsx-gherkin/compare/v2.0.0...v2.0.1) (2026-10-21)
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
### Bug Fixes
|
|
5
|
+
|
|
6
|
+
* **skill:** state that inline step comments are preserved step text ([7e49eae](https://github.com/aquine-kujaruk/opsx-gherkin/commit/7e49eae1fe3beb7049f7817ce84309e216ea1745))
|
|
7
|
+
|
|
1
8
|
# [2.0.0](https://github.com/aquine-kujaruk/opsx-gherkin/compare/v1.0.1...v2.0.0) (2026-10-20)
|
|
2
9
|
|
|
3
10
|
|
package/package.json
CHANGED
|
@@ -69,6 +69,8 @@ These examples apply the canonical contract to their own domains.
|
|
|
69
69
|
and none is required: a new document may omit them, but conversion preserves
|
|
70
70
|
every supplied tag unchanged. Authoring conventions do not narrow syntax
|
|
71
71
|
acceptance.
|
|
72
|
+
- An HTML comment at the end of a step is step text: every conversion
|
|
73
|
+
preserves it verbatim, and it has no meaning to the converter.
|
|
72
74
|
- In MDG, put each tag in its own backtick span immediately above the tagged
|
|
73
75
|
heading. In native Gherkin, use bare tags. Reserve `@openspec-*` and `@mdg-*`
|
|
74
76
|
names for the structural roles defined by the contract.
|
|
@@ -165,7 +165,7 @@ The converter SHALL map a Gherkin Feature to an OpenSpec title and Purpose, and
|
|
|
165
165
|
|
|
166
166
|
## Rule: Preserve behavioral Gherkin constructs
|
|
167
167
|
|
|
168
|
-
The converter SHALL preserve Scenario and Scenario Outline structure, typed steps, tags, Examples, Data Tables, and Doc Strings without treating them as opaque prose.
|
|
168
|
+
The converter SHALL preserve Scenario and Scenario Outline structure, typed steps, tags, Examples, Data Tables, and Doc Strings without treating them as opaque prose. An inline HTML comment inside a step's text is step text and SHALL be preserved verbatim.
|
|
169
169
|
|
|
170
170
|
Canonical MDG and OpenSpec tables SHALL carry one Markdown separator row directly after their indented header; canonical plain Gherkin tables SHALL omit it. Compatible MDG inputs with or without separators SHALL preserve the same interpreted rows and values.
|
|
171
171
|
|
|
@@ -230,6 +230,21 @@ Canonical MDG and OpenSpec tables SHALL carry one Markdown separator row directl
|
|
|
230
230
|
| MDG | OpenSpec |
|
|
231
231
|
| OpenSpec | MDG |
|
|
232
232
|
|
|
233
|
+
### Scenario Outline: Preserve an inline step comment in `<target_format>`
|
|
234
|
+
|
|
235
|
+
* Given a compatible `<source_format>` main spec or delta whose step text ends with an inline HTML comment such as `<!-- addUnits -->`
|
|
236
|
+
* When it is converted to `<target_format>`
|
|
237
|
+
* Then the step text, including the comment, is unchanged
|
|
238
|
+
* And the converter attaches no meaning to the comment
|
|
239
|
+
|
|
240
|
+
#### Examples: Comment conversion directions
|
|
241
|
+
|
|
242
|
+
| source_format | target_format |
|
|
243
|
+
| --- | --- |
|
|
244
|
+
| OpenSpec | MDG |
|
|
245
|
+
| MDG | OpenSpec |
|
|
246
|
+
| OpenSpec | plain Gherkin |
|
|
247
|
+
|
|
233
248
|
## Rule: Project OpenSpec to a plain Gherkin feature
|
|
234
249
|
|
|
235
250
|
The `opsx-to-feature` command SHALL preserve the same normalized behavioral model as `opsx-to-mdg` and MUST emit plain-text Gherkin accepted by the official parser.
|