Feature Request: Add Support for Gherkin .feature Files (Including Use in “Unused Keywords” Analysis)

[PcGnCLwnCm9EgY56mAmL]

Please add native support in RoboView for parsing and visualizing Gherkin .feature files, similar to existing support for .robot files. This includes ensuring .feature files are incorporated into keyword usage analysis — especially the “Unused Keywords” functionality.

Teams increasingly use Gherkin syntax together with Robot Framework thanks to tools like:
https://github.com/robotcodedev/robotframework-gherkin-parser

These tools allow .feature files to run as Robot Framework tests.
However: RoboView does not scan .feature files, so keywords used only inside Gherkin scenarios are not detected.
This leads to incorrect “Unused Keyword” results — RoboView reports keywords as unused even though they are actually used inside .feature file

for example in a .feature file:

    And I open instrument TEST SHARE ABC  by search type symbol

corresponding keyword in a resource file:

I Open Instrument ${instrument} By Search Type ${search type}
    [Documentation]    Search and open a specific instrument
    Search For Instrument ${instrument} By Search Type ${search type}
    Click    ${first search result}

Another example with examples:

feature file:
  Scenario: Should set the value to the most used value of every type
    When I set value <type> with id <id> and distribution 100
    And I save the values
    Then the value should be saved
    And the type should contain "<classification_type_dutch>"
    And the id should be "<classification_dutch>"
    And the distribution should be 100

    Examples:
      | type         | id                          | classification_type_dutch    | classification_dutch                    |
      | a                | aid               | Alternatieven                | Niet gespecificeerd                     |
      | b             | bid              | Soort              | Bedrijf