Migrates multiline_names feature to new structure

[chrismdp]

No description provided.

[mattwynne]

We should update this feature. The correct terminology is that the elements break down like this:

Feature: Feature name (single line)
  This is the description, which is different to the name
  and can span over multiple lines.

  We can even have blank lines, we just mustn't mention a 
  magic word like `Background:` or `Scenario:` at the beginning
  of a line otherwise Gherkin will start to pay attention.

  That's the end of the description.

So the feature itself should be called 'multiline descriptions' and the examples (and their indentation) should be changed so the terminology is clear.

[chrismdp]

I've incorporated the spirit of what's going on into the feature. I've dropped 'multiline' as that doesn't really make sense to a reader, and it's implicit in the feature.

[mattwynne]

Name of this file is still a bit dodgy! :)

[chrismdp]

Thanks for the detailed feedback - helps very much as I ease into the codebase :) I've incorporated it into the latest commit.

[mattwynne]

line -> lines

[chrismdp]

More feedback changes incorporated.

[mattwynne]

The indentation is out here, or it appears to be on the GH rendering of the diff. It should be left-aligned with the first " of the """

[chrismdp]

Fixed.

[mattwynne]

Thanks Chris!

[tooky]

On Thursday, 16 May 2013 at 11:11, Matt Wynne wrote:

Thanks Chris!

👍

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.