Problem description
Gherkin linting (gplint with the CAMARA configuration from camaraproject/tooling) reports 128 mechanical findings over artifacts/testing/*.feature: 121× indentation and 7× no-trailing-spaces.
| File |
indentation |
no-trailing-spaces |
C01-device-errors.feature |
70 |
3 |
C02-phoneNumber-errors.feature |
45 |
1 |
event-subscription-template.feature |
2 |
— |
sample-service-template.feature |
4 |
1 |
sample-implicit-events-template.feature |
— |
2 |
The feature templates are the starting point API repositories copy, and API test definitions are lint-checked against exactly this style — the templates should exhibit it. Since #673 the findings are visible as warnings in the Artifacts Lint workflow log on every PR.
Expected behavior
Reformat the feature files to the configured indentation scheme (Feature 0, Background/Scenario 2, steps 4, Examples 4, rows 6) and remove trailing spaces, bringing the mechanical warning count to zero. No semantic changes.
Alternative solution
None — purely mechanical.
Additional context
The remaining gplint warnings (no-dupe-scenario-names, no-unused-variables) are template-natured and are handled in the expected-warnings documentation issue instead. Line endings of three of these files are normalized in #674; that should land first or together. Part of the warnings follow-up noted on #668.
Problem description
Gherkin linting (gplint with the CAMARA configuration from
camaraproject/tooling) reports 128 mechanical findings overartifacts/testing/*.feature: 121×indentationand 7×no-trailing-spaces.C01-device-errors.featureC02-phoneNumber-errors.featureevent-subscription-template.featuresample-service-template.featuresample-implicit-events-template.featureThe feature templates are the starting point API repositories copy, and API test definitions are lint-checked against exactly this style — the templates should exhibit it. Since #673 the findings are visible as warnings in the Artifacts Lint workflow log on every PR.
Expected behavior
Reformat the feature files to the configured indentation scheme (Feature 0, Background/Scenario 2, steps 4, Examples 4, rows 6) and remove trailing spaces, bringing the mechanical warning count to zero. No semantic changes.
Alternative solution
None — purely mechanical.
Additional context
The remaining gplint warnings (
no-dupe-scenario-names,no-unused-variables) are template-natured and are handled in the expected-warnings documentation issue instead. Line endings of three of these files are normalized in #674; that should land first or together. Part of the warnings follow-up noted on #668.