opsx-gherkin 2.0.1 → 2.0.2
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 +7 -0
- package/package.json +1 -1
- package/skills/opsx-gherkin/SKILL.md +22 -6
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,10 @@
|
|
|
1
|
+
## [2.0.2](https://github.com/aquine-kujaruk/opsx-gherkin/compare/v2.0.1...v2.0.2) (2026-10-22)
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
### Bug Fixes
|
|
5
|
+
|
|
6
|
+
* **skill:** update SKILL.md to clarify Gherkin table formatting and conversion requirements ([377026d](https://github.com/aquine-kujaruk/opsx-gherkin/commit/377026dea6a581beeba23cdbebded59e505555db))
|
|
7
|
+
|
|
1
8
|
## [2.0.1](https://github.com/aquine-kujaruk/opsx-gherkin/compare/v2.0.0...v2.0.1) (2026-10-21)
|
|
2
9
|
|
|
3
10
|
|
package/package.json
CHANGED
|
@@ -90,6 +90,12 @@ Examples cases or Data Table values. Use `\|` for a literal pipe, `\\` for a
|
|
|
90
90
|
literal backslash, and `\n` for a newline inside a cell. Do not apply cell
|
|
91
91
|
escaping to Doc Strings.
|
|
92
92
|
|
|
93
|
+
A Markdown table is a Gherkin table only while every row keeps its two-space
|
|
94
|
+
indentation. A project Markdown formatter, such as oxfmt or prettier, removes it,
|
|
95
|
+
and conversion then fails with `Examples "<heading>" has no table`, while
|
|
96
|
+
`validate-spec --format openspec` can still accept the file. Exclude
|
|
97
|
+
`openspec/**` from formatting before the first conversion.
|
|
98
|
+
|
|
93
99
|
Keep a Markdown Doc String in a triple-backtick block indented by two spaces
|
|
94
100
|
under its step; put its optional media type immediately after the opening fence.
|
|
95
101
|
Preserve the content's indentation relative to the fence. In an outline, each
|
|
@@ -98,16 +104,26 @@ verify the expanded cases.
|
|
|
98
104
|
|
|
99
105
|
## Convert and verify
|
|
100
106
|
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
107
|
+
When an OpenSpec spec exists, it is the source. A Gherkin rendering of it
|
|
108
|
+
(`.feature`, `.feature.md`) is derived and exists only as a stream: convert to
|
|
109
|
+
stdout and pipe the result into its consumer. Never write the rendering next to
|
|
110
|
+
the spec or anywhere else in the working tree; a copy drifts as soon as the spec
|
|
111
|
+
changes. Use `-o <destination>` only to author a spec from Markdown with Gherkin
|
|
112
|
+
the user supplied (`mdg-to-opsx`), or for a rendering the user explicitly asked
|
|
113
|
+
for by name and destination. Existing outputs require `--force`. Respect the
|
|
114
|
+
user's destination and overwrite intent.
|
|
104
115
|
|
|
105
116
|
```sh
|
|
117
|
+
opsx-gherkin opsx-to-feature spec.md | <consumer> --stdin
|
|
118
|
+
opsx-gherkin opsx-to-mdg spec.md | <consumer> --stdin
|
|
106
119
|
opsx-gherkin mdg-to-opsx input.feature.md -o spec.md
|
|
107
|
-
opsx-gherkin opsx-to-mdg spec.md -o output.feature.md
|
|
108
|
-
opsx-gherkin opsx-to-feature spec.md -o output.feature
|
|
109
120
|
```
|
|
110
121
|
|
|
122
|
+
Each converter accepts one path, `--text`, or stdin. Read the consumer's own
|
|
123
|
+
help for how it takes standard input. If conversion reports that an Examples
|
|
124
|
+
group has no table, see the formatter caveat under "Keep table and argument
|
|
125
|
+
values intact".
|
|
126
|
+
|
|
111
127
|
Use `--name` when OpenSpec text has no title or usable source-path context.
|
|
112
128
|
`--project-root` supplies existing main-spec context for delta validation when
|
|
113
129
|
needed. Consult a converter's `--help` for its exact options.
|
|
@@ -124,7 +140,7 @@ checks model preservation.
|
|
|
124
140
|
```sh
|
|
125
141
|
validate-spec --format openspec spec.md
|
|
126
142
|
validate-spec --format mdg input.feature.md
|
|
127
|
-
validate-spec --format feature
|
|
143
|
+
opsx-gherkin opsx-to-feature spec.md | validate-spec --format feature /dev/stdin
|
|
128
144
|
```
|
|
129
145
|
|
|
130
146
|
Passing these checks establishes example syntax and conversion preservation.
|