Is the "Rule" keyword supported?

In the Gherkin v6 spec, the Rule keyword was added.

When I add this keyword, a parsing exception is thrown:

CompositeParserException: Parser errors:
(12:3): expected: #EOF, #TableRow, #DocStringSeparator, #StepLine, #TagLine, #ScenarioLine, 
#ScenarioOutlineLine, #Comment, #Empty, got 'Rule: 

Are there any plans to include the keyword, or is it not yet on the roadmap since it hasn’t been incorporated into all implementations of Cucumber yet?

[irahov]

I’d like to emphasize the importance of Rule support, especially in big projects. If you think that cypress-cucumber-preprocessor is suitable for enterprise projects please do add that support or at least provide some feedback when this can be expected.

The current behavior is a bit strange. I add just one Rule: and Background: in it. - OK I add two rules - NOT OK I add Feature: Background: Rule: - NOT OK

By NOT OK I mean there is a parse error:

Error: Webpack Compilation Error
./cypress/integration/edge-gateway-l2vpn.feature
Module build failed (from ./node_modules/cypress-cucumber-preprocessor/loader.js):
CompositeParserException: Parser errors:

[irahov]

Hi, With my previous note, I didn’t mean to be harsh. I’m sorry for that. My frustration came from the fact that people were asking questions and there had been no responses for months even for more than half a year. Also when I used ‘enerprise’ I didn’t mean ‘a company’, but rather something serious. Also a MIT project doesn’t mean lots of features and fulfilling everybody’s desires, but it also does not exclude accountability, where the maintainers answer questions. Once again I’m sorry if I had been harsh.