Interface: GherkinPluginOptions
@termwright/gherkin / GherkinPluginOptions
Interface: GherkinPluginOptions<Fixtures>
Section titled “Interface: GherkinPluginOptions<Fixtures>”Defined in: plugin.ts:43
Options for a Gherkin transform using an optional project fixture surface.
Type Parameters
Section titled “Type Parameters”Fixtures
Section titled “Fixtures”Fixtures extends object = Record<string, unknown>
Properties
Section titled “Properties”featureRoot?
Section titled “featureRoot?”
readonlyoptionalfeatureRoot?:string
Defined in: plugin.ts:45
Directory against which feature paths and pairing templates are resolved. Defaults to Vite’s root.
fixtureNames?
Section titled “fixtureNames?”
readonlyoptionalfixtureNames?: readonlyExclude<Extract<keyofFixtures,string>,GherkinReservedFixtureName>[]
Defined in: plugin.ts:60
Custom test.extend() fixture names forwarded into every Gherkin context.
generatedImports?
Section titled “generatedImports?”
readonlyoptionalgeneratedImports?:GeneratedGherkinImports
Defined in: plugin.ts:58
Module specifiers emitted into transformed feature files.
includeFeatures?
Section titled “includeFeatures?”
readonlyoptionalincludeFeatures?:boolean
Defined in: plugin.ts:56
Add physical .feature files to Vitest discovery. Used by managed hosts
such as termwright ui.
The feature patterns are derived from the resolved Vitest test.include
patterns. This deliberately does not widen a narrowly configured suite to
every feature below the project root.
stepDefinitions?
Section titled “stepDefinitions?”
readonlyoptionalstepDefinitions?: readonlystring[]
Defined in: plugin.ts:47
Cypress-compatible [filepath] / [filepart] glue patterns.
readonlyoptionaltags?:string
Defined in: plugin.ts:65
Cucumber tag expression selecting Scenario and Outline cases.