middleman-core 4.3.11 → 5.0.0.rc.1

data/features/automatic_image_sizes.feature

@@ -1,29 +0,0 @@
-Feature: Automatically detect and insert image dimensions into tags
-  In order to speed up development and appease YSlow
-
-  Scenario: Rendering an image with the feature disabled
-    Given a fixture app "automatic-image-size-app"
-    And a file named "config.rb" with:
-      """
-      """
-    And the Server is running at "automatic-image-size-app"
-    When I go to "/auto-image-sizes.html"
-    Then I should not see "width="
-    And I should not see "height="
-    When I go to "/markdown-sizes.html"
-    Then I should not see "width="
-    And I should not see "height="
-
-  Scenario: Rendering an image with the feature enabled
-    Given a fixture app "automatic-image-size-app"
-    And a file named "config.rb" with:
-      """
-      activate :automatic_image_sizes
-      """
-    And the Server is running at "automatic-image-size-app"
-    When I go to "/auto-image-sizes.html"
-    Then I should see 'width="1"'
-    And I should see 'height="1"'
-    When I go to "/markdown-sizes.html"
-    Then I should see 'width="1"'
-    And I should see 'height="1"'

data/features/builder.feature

@@ -1,61 +0,0 @@
-Feature: Builder
-  In order to output static html and css for delivery
-
-  Scenario: Checking built folder for content
-    Given a successfully built app at "large-build-app"
-    When I cd to "build"
-    Then the following files should exist:
-      | index.html                                    |
-      | static.html                                   |
-      | services/index.html                           |
-      | stylesheets/static.css                        |
-      | images/blank.gif                              |
-      | images/Read me (example).txt                  |
-      | images/Child folder/regular_file(example).txt |
-      | .htaccess                                     |
-      | .htpasswd                                     |
-      | feed.xml                                      |
-    Then the following files should not exist:
-      | _partial                                      |
-      | layout                                        |
-      | layouts/custom                                |
-      | layouts/content_for                           |
-
-    And the file "index.html" should contain "Comment in layout"
-    And the file "index.html" should contain "<h1>Welcome</h1>"
-    And the file "static.html" should contain "Static, no code!"
-    And the file "services/index.html" should contain "Services"
-    And the file "stylesheets/static.css" should contain "body"
-
-  Scenario: Build glob
-    Given a successfully built app at "glob-app" with flags "--glob '*.css'"
-    When I cd to "build"
-    Then the following files should not exist:
-      | index.html                                    |
-    Then the following files should exist:
-      | stylesheets/site.css                          |
-
-  Scenario: Build with errors
-    Given a built app at "build-with-errors-app"
-    Then the exit status should be 1
-
-  Scenario: Build empty errors
-    Given a built app at "empty-app"
-    Then the exit status should be 1
-
-  Scenario: Build external_pipeline errors
-    Given a built app at "external-pipeline-error"
-    Then the exit status should be 1
-
-  Scenario: Build alias (b)
-    Given a fixture app "large-build-app"
-    When I run `middleman b`
-    Then was successfully built
-
-  Scenario: Builded text file(ex: html, css, xml, txt)'s permission is 0644
-    Given a successfully built app at "large-build-app"
-    When I cd to "build"
-    Then the mode of filesystem object "index.html" should match "0644"
-    And the mode of filesystem object "stylesheets/static.css" should match "0644"
-    And the mode of filesystem object "feed.xml" should match "0644"
-    And the mode of filesystem object ".htaccess" should match "0644"

data/features/cache_buster.feature

@@ -1,56 +0,0 @@
-Feature: Generate mtime-based query string for busting browser caches
-  In order to display the most recent content for IE & CDNs and appease YSlow
-    
-  Scenario: Rendering css with the feature disabled
-    Given "cache_buster" feature is "disabled"
-    And the Server is running at "cache-buster-app"
-    When I go to "/stylesheets/relative_assets.css"
-    Then I should see 'blank.gif"'
-    
-  Scenario: Rendering html with the feature disabled
-    Given "cache_buster" feature is "disabled"
-    And the Server is running at "cache-buster-app"
-    When I go to "/cache-buster.html"
-    Then I should see 'site.css"'
-
-  Scenario: Rendering css with the feature enabled
-    Given "cache_buster" feature is "enabled"
-    And the Server is running at "cache-buster-app"
-    When I go to "/stylesheets/relative_assets.css"
-    Then I should see "blank.gif?"
-
-  Scenario: Rendering html with the feature enabled
-    Given "cache_buster" feature is "enabled"
-    And the Server is running at "cache-buster-app"
-    When I go to "/cache-buster.html"
-    Then I should see "site.css?"
-    Then I should see "blank.gif?"
-
-  Scenario: Rendering css with the feature and relative_assets enabled
-    Given "relative_assets" feature is "enabled"
-    Given "cache_buster" feature is "enabled"
-    And the Server is running at "cache-buster-app"
-    When I go to "/stylesheets/relative_assets.css"
-    Then I should see "blank.gif?"
-
-  Scenario: Rendering html with the feature and relative_assets enabled
-    Given "relative_assets" feature is "enabled"
-    Given "cache_buster" feature is "enabled"
-    And the Server is running at "cache-buster-app"
-    When I go to "/cache-buster.html"
-    Then I should see "site.css?"
-    Then I should see "blank.gif?"
-
-  Scenario: URLs are not rewritten for rewrite ignored paths
-    Given a fixture app "cache-buster-app"
-    And a file named "config.rb" with:
-      """
-      activate :cache_buster, rewrite_ignore: [
-        '/cache-buster.html',
-      ]
-      """
-    And the Server is running at "cache-buster-app"
-    When I go to "/cache-buster.html"
-    Then I should see 'site.css"'
-    Then I should see 'empty-with-include.js"'
-    Then I should see 'blank.gif"'

data/features/capture_html.feature

@@ -1,18 +0,0 @@
-@wip
-
-Feature: Support capture_html and yield_content helpers
-
-  Scenario: content_for works as expected in erb
-    Given the Server is running at "capture-html-app"
-    When I go to "/capture_html_erb.html"
-    Then I should see "In Layout: <h1>I am the yielded content erb</h1>"
-    
-  Scenario: content_for works as expected in haml
-    Given the Server is running at "capture-html-app"
-    When I go to "/capture_html_haml.html"
-    Then I should see "In Layout: <h1>I am the yielded content haml</h1>"
-    
-  Scenario: content_for works as expected in slim
-    Given the Server is running at "capture-html-app"
-    When I go to "/capture_html_slim.html"
-    Then I should see "In Layout: <h1>I am the yielded content slim</h1>"

data/features/chained_templates.feature

@@ -1,109 +0,0 @@
-Feature: Templates should be chainable
-  In order to insert variables and data in "static" engines
-
-  Scenario: Data in Erb in Markdown
-    Given the Server is running at "chained-app"
-    When I go to "/index.html"
-    Then I should see "Title</h1>"
-    And I should see "Subtitle</h2>"
-    And I should see "Sup</h3>"
-
-  Scenario: Build chained template
-    Given a successfully built app at "chained-app"
-    When I cd to "build"
-    Then the following files should exist:
-      | index.html                                    |
-      | test.erb.combobreaker                         |
-    And the file "index.html" should contain "Title</h1>"
-    And the file "index.html" should contain "Subtitle</h2>"
-    And the file "index.html" should contain "Sup</h3>"
-    And the file "test.erb.combobreaker" should contain "Title</h1>"
-    And the file "test.erb.combobreaker" should contain "Subtitle</h2>"
-    And the file "test.erb.combobreaker" should contain "Sup</h3>"
-
-  Scenario: Partials are parsed by multiple template engines: Outer template has .erb and inner .md.erb
-    Given a fixture app "partial-chained_templates-app"
-    And a template named "my_template.html.erb" with:
-    """
-    <h1>My Template</h1>
-
-    <%= partial 'my_partial' %>
-    """
-    And a template named "my_partial.html.md.erb" with:
-    """
-    ## My Partial
-
-    <%= 'hello world' %>
-    """
-    And the Server is running
-    When I go to "/my_template.html"
-    Then I should see:
-    """
-    <h1>My Template</h1>
-    """
-    Then I should see:
-    """
-    <h2 id="my-partial">My Partial</h2>
-    """
-    Then I should see:
-    """
-    <p>hello world</p>
-    """
-
-  Scenario: Partials are parsed by multiple template engines: Outer template has .md.erb and inner .md.erb
-    Given a fixture app "partial-chained_templates-app"
-    And a template named "my_template.html.md.erb" with:
-    """
-    # My Template
-
-    <%= partial 'my_partial' %>
-    """
-    And a template named "my_partial.html.md.erb" with:
-    """
-    ## My Partial
-
-    <%= 'hello world' %>
-    """
-    And the Server is running
-    When I go to "/my_template.html"
-    Then I should see:
-    """
-    <h1 id="my-template">My Template</h1>
-    """
-    Then I should see:
-    """
-    <h2 id="my-partial">My Partial</h2>
-    """
-    Then I should see:
-    """
-    <p>hello world</p>
-    """
-
-  Scenario: Partials are parsed by multiple template engines: Outer template has .md.erb, and inner .erb
-    Given a fixture app "partial-chained_templates-app"
-    And a template named "my_template.html.md.erb" with:
-    """
-    # My Template
-
-    <%= partial 'my_partial' %>
-    """
-    And a template named "my_partial.html.erb" with:
-    """
-    <h2>My Partial</h2>
-
-    <%= 'hello world' %>
-    """
-    And the Server is running
-    When I go to "/my_template.html"
-    Then I should see:
-    """
-    <h1 id="my-template">My Template</h1>
-    """
-    Then I should see:
-    """
-    <h2>My Partial</h2>
-    """
-    Then I should see:
-    """
-    <p>hello world</p>
-    """

data/features/clean_build.feature

@@ -1,78 +0,0 @@
-Feature: Build Clean
-  Scenario: Build and Clean an app
-    Given a fixture app "clean-app"
-    And app "clean-app" is using config "empty"
-    And a successfully built app at "clean-app" with flags "--no-clean"
-    Then the following files should exist:
-      | build/index.html              |
-      | build/should_be_ignored.html  |
-      | build/should_be_ignored2.html |
-      | build/should_be_ignored3.html |
-    And app "clean-app" is using config "complications"
-    Given a successfully built app at "clean-app"
-    Then the following files should not exist:
-      | build/should_be_ignored.html  |
-      | build/should_be_ignored2.html |
-      | build/should_be_ignored3.html |
-    And the file "build/index.html" should contain "Comment in layout"
-
-  Scenario: Clean build has a whitelist
-    Given a fixture app "clean-app"
-    When a file named "build/.test" with:
-      """
-      Hello
-      """
-    When a file named "config.rb" with:
-      """
-      set :skip_build_clean do |path|
-        path =~ /\.test/
-      end
-      """
-    Given a built app at "clean-app"
-    Then the following files should exist:
-      | build/.test         |
-
-  Scenario: Clean build an app with newly ignored files and a nested output directory
-    Given a fixture app "clean-nested-app"
-    When a file named "config.rb" with:
-      """
-      set :build_dir, "sub/dir"
-      """
-    Given a built app at "clean-nested-app" with flags "--no-clean"
-    Then a directory named "sub/dir" should exist
-    Then the following directories should exist:
-      | sub/dir                    |
-      | sub/dir/nested             |
-    Then the following files should exist:
-      | sub/dir/about.html         |
-      | sub/dir/nested/nested.html |
-    When a file named "config.rb" with:
-      """
-      set :build_dir, "sub/dir"
-      ignore 'about.html'
-      ignore 'nested/*'
-      """
-    Given a built app at "clean-nested-app"
-    Then the following directories should not exist:
-      | sub/dir/nested             |
-    Then the following files should not exist:
-      | sub/dir/about.html         |
-      | sub/dir/nested/nested.html |
-
-  Scenario: Build and clean an app under a hidden directory
-    Given a fixture app "clean-app"
-    And app "clean-app" is using config "hidden-dir-before"
-    And a built app at "clean-app"
-    Then the following files should exist:
-      | .build/index.html              |
-      | .build/should_be_ignored.html  |
-      | .build/should_be_ignored2.html |
-      | .build/should_be_ignored3.html |
-    Given app "clean-app" is using config "hidden-dir-after"
-    And a built app at "clean-app"
-    Then the following files should exist:
-      | .build/index.html              |
-    And the following files should not exist:
-      | .build/should_be_ignored.html  |
-      | .build/should_be_ignored2.html |
-      | .build/should_be_ignored3.html |

data/features/coffee-script.feature

@@ -1,22 +0,0 @@
-Feature: Support coffee-script
-  In order to offer an alternative when writing Javascript
-
-  Scenario: Rendering coffee script
-    Given the Server is running at "coffeescript-app"
-    When I go to "/javascripts/coffee_test.js"
-    Then I should see ".slice"
-
-  Scenario: Rendering coffee-script with :coffeescript haml-filter
-    Given the Server is running at "coffeescript-app"
-    When I go to "/inline-coffeescript.html"
-    Then I should see ".slice"
-  
-  Scenario: Rendering broken coffee
-    Given the Server is running at "coffeescript-app"
-    When I go to "/javascripts/broken-coffee.js"
-    Then I should see "reserved word"
-  
-  Scenario: Building broken coffee
-    Given a built app at "coffeescript-app"
-    Then the output should contain "error  build/javascripts/broken-coffee.js"
-    And the exit status should be 1

data/features/collections.feature

@@ -1,265 +0,0 @@
-Feature: Collections
-  Scenario: Lazy query
-    Given a fixture app "collections-app"
-    And a file named "config.rb" with:
-      """
-      articles1 = collection :articles1, resources.select { |r|
-        matcher = ::Middleman::Util::UriTemplates.uri_template('blog1/{year}-{month}-{day}-{title}.html')
-        ::Middleman::Util::UriTemplates.extract_params(matcher, ::Middleman::Util.normalize_path(r.url))
-      }
-
-      everything = resources.select do |r|
-        true
-      end
-
-      def get_tags(resource)
-        if resource.data.tags.is_a? String
-          resource.data.tags.split(',').map(&:strip)
-        else
-          resource.data.tags
-        end
-      end
-
-      def group_lookup(resource, sum)
-        results = Array(get_tags(resource)).map(&:to_s).map(&:to_sym)
-
-        results.each do |k|
-          sum[k] ||= []
-          sum[k] << resource
-        end
-      end
-
-      tags = everything
-          .select { |resource| resource.data.tags }
-          .each_with_object({}, &method(:group_lookup))
-
-      class Wrapper
-        attr_reader :stuff
-
-        def initialize
-          @stuff = Set.new
-        end
-
-        def <<((k, v))
-          @stuff << k
-          self
-        end
-      end
-
-      collection :wrapped, tags.reduce(Wrapper.new, :<<)
-
-      set :tags, tags # Expose to templates
-
-      collection :first_tag, tags.keys.sort.first
-      """
-    And a file named "source/index.html.erb" with:
-      """
-      <% collection(:articles1).each do |article| %>
-        Article1: <%= article.data.title %>
-      <% end %>
-
-      Tag Count: <%= collection(:wrapped).stuff.length %>
-
-      <% config[:tags].value.each do |k, items| %>
-        Tag: <%= k %> (<%= items.length %>)
-        <% items.each do |article| %>
-          Article (<%= k %>): <%= article.data.title %>
-        <% end %>
-      <% end %>
-
-      First Tag: <%= collection(:first_tag) %>
-      """
-    Given the Server is running at "collections-app"
-    When I go to "index.html"
-    Then I should see 'Article1: Blog1 Newer Article'
-    And I should see 'Article1: Blog1 Another Article'
-    And I should see 'Tag: foo (4)'
-    And I should see 'Article (foo): Blog1 Newer Article'
-    And I should see 'Article (foo): Blog1 Another Article'
-    And I should see 'Article (foo): Blog2 Newer Article'
-    And I should see 'Article (foo): Blog2 Another Article'
-    And I should see 'Tag: bar (2)'
-    And I should see 'Article (bar): Blog1 Newer Article'
-    And I should see 'Article (bar): Blog2 Newer Article'
-    And I should see 'Tag: 120 (1)'
-    And I should see 'Article (120): Blog1 Another Article'
-    And I should see 'First Tag: 120'
-    And I should see 'Tag Count: 3'
-
-  Scenario: Collected resources update with file changes
-    Given a fixture app "collections-app"
-    And a file named "config.rb" with:
-      """
-      collection :articles, resources.select { |r|
-        matcher = ::Middleman::Util::UriTemplates.uri_template('blog2/{year}-{month}-{day}-{title}.html')
-        ::Middleman::Util::UriTemplates.extract_params(matcher, ::Middleman::Util.normalize_path(r.url))
-      }
-      """
-    And a file named "source/index.html.erb" with:
-      """
-      <% collection(:articles).each do |article| %>
-        Article: <%= article.data.title || article.file_descriptor[:relative_path] %>
-      <% end %>
-      """
-    Given the Server is running at "collections-app"
-    When I go to "index.html"
-    Then I should not see "Article: index.html.erb"
-    Then I should see 'Article: Blog2 Newer Article'
-    And I should see 'Article: Blog2 Another Article'
-
-    And the file "source/blog2/2011-01-02-another-article.html.markdown" has the contents
-      """
-      ---
-      title: "Blog3 Another Article"
-      date: 2011-01-02
-      tags:
-        - foo
-      ---
-
-      Another Article Content
-
-      """
-    When I go to "index.html"
-    Then I should see "Article: Blog2 Newer Article"
-    And I should not see "Article: Blog2 Another Article"
-    And I should see 'Article: Blog3 Another Article'
-
-    And the file "source/blog2/2011-01-01-new-article.html.markdown" is removed
-    When I go to "index.html"
-    Then I should not see "Article: Blog2 Newer Article"
-    And I should see 'Article: Blog3 Another Article'
-
-    And the file "source/blog2/2014-01-02-yet-another-article.html.markdown" has the contents
-      """
-      ---
-      title: "Blog2 Yet Another Article"
-      date: 2011-01-02
-      tags:
-        - foo
-      ---
-
-      Yet Another Article Content
-      """
-    When I go to "index.html"
-    And I should see 'Article: Blog3 Another Article'
-    And I should see 'Article: Blog2 Yet Another Article'
-
-  Scenario: Work with local helpers
-    Given a fixture app "collections-app"
-    And a file named "config.rb" with:
-      """
-      module TestHelper
-        def help_me
-          "ok"
-        end
-      end
-
-      include TestHelper
-
-      data.articles.each_with_index do |a, i|
-        proxy "/#{i}-#{help_me}.html", a
-      end
-      """
-    And a file named "data/articles.yaml" with:
-      """
-      ---
-      - "/blog1/2011-01-01-new-article.html"
-      - "/blog2/2011-01-02-another-article.html"
-      """
-    Given the Server is running at "collections-app"
-    When I go to "0-ok.html"
-    Then I should see 'Newer Article Content'
-    When I go to "1-ok.html"
-    Then I should see 'Another Article Content'
-
-  Scenario: Collected data update with file changes
-    Given a fixture app "collections-app"
-    And a file named "config.rb" with:
-      """
-      data.articles.each_with_index do |a, i|
-        proxy "/#{i}.html", a
-      end
-      """
-    And a file named "data/articles.yaml" with:
-      """
-      ---
-      - "/blog1/2011-01-01-new-article.html"
-      - "/blog2/2011-01-02-another-article.html"
-      """
-    Given the Server is running at "collections-app"
-    When I go to "0.html"
-    Then I should see 'Newer Article Content'
-    When I go to "1.html"
-    Then I should see 'Another Article Content'
-    When I go to "2.html"
-    Then I should see 'Not Found'
-
-    When the file "data/articles.yaml" has the contents
-      """
-      ---
-      - "/blog1/2011-01-01-new-article.html"
-      """
-    When I go to "0.html"
-    Then I should see 'Newer Article Content'
-    When I go to "1.html"
-    Then I should see 'Not Found'
-    When I go to "2.html"
-    Then I should see 'Not Found'
-
-    When the file "data/articles.yaml" has the contents
-      """
-      ---
-      - "/blog2/2011-01-02-another-article.html"
-      - "/blog1/2011-01-01-new-article.html"
-      - "/blog2/2011-01-01-new-article.html"
-      """
-    When I go to "0.html"
-    Then I should see 'Another Article Content'
-    When I go to "1.html"
-    Then I should see 'Newer Article Content'
-    When I go to "2.html"
-    Then I should see 'Again'
-
-  Scenario: Arbitrary live datasets
-    Given a fixture app "collections-app"
-    And a file named "config.rb" with:
-      """
-      ignore "/description_template.html"
-
-      live {
-        Dir[File.join(root, "descriptions/*.txt")]
-      }.each do |description_name|
-        base = File.basename(description_name, '.txt')
-        proxy "#{base}.html", "/description_template.html", locals: {
-          contents: File.read(description_name)
-        }
-      end
-      """
-    And a file named "source/description_template.html.erb" with:
-      """
-      <%= contents %>
-      """
-    And a file named "descriptions/test1.txt" with:
-      """
-      Test1
-      """
-    Given the Server is running at "collections-app"
-    When I go to "test1.html"
-    Then I should see 'Test1'
-    When I go to "test2.html"
-    Then I should see 'Not Found'
-
-    When the file "descriptions/test2.txt" has the contents
-      """
-      Test2
-      """
-    When I go to "test1.html"
-    Then I should see 'Test1'
-    When I go to "test2.html"
-    Then I should see 'Test2'
-
-    When the file "descriptions/test1.txt" is removed
-    When I go to "test1.html"
-    Then I should see 'Not Found'
-    When I go to "test2.html"
-    Then I should see 'Test2'