locomotive_cms 2.0.0.rc12 → 2.0.0

data/features/api/content_types.feature

@@ -0,0 +1,156 @@
+Feature: Content Types
+  In order to manage content types programmatically
+  As an API user
+  I will be able to create and update content types
+
+  Background:
+    Given I have the site: "test site" set up
+    And I have an "admin" API token
+
+  Scenario: Creating Content Type with order_by
+    When I do an API POST to content_types.json with:
+    """
+    {
+      "content_type": {
+        "name": "Employees",
+        "slug": "employees",
+        "order_by": "name",
+        "entries_custom_fields": [
+          {
+            "label": "Name",
+            "name": "name",
+            "type": "string"
+          },
+          {
+            "label": "Position",
+            "name": "position",
+            "type": "string"
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to content_types.json
+    Then the JSON response should be an array
+    And the JSON response should have 1 entry
+    When I keep the JSON response at "0/entries_custom_fields/0/id" as "ORDER_BY_ATTRIBUTE_ID"
+    Then the JSON response at "0/order_by" should be %{ORDER_BY_ATTRIBUTE_ID}
+    And the JSON response at "0/order_by_field_name" should be "name"
+
+  Scenario: Creating Content Type with special order_by
+    When I do an API POST to content_types.json with:
+    """
+    {
+      "content_type": {
+        "name": "Employees",
+        "slug": "employees",
+        "order_by": "updated_at",
+        "entries_custom_fields": [
+          {
+            "label": "Name",
+            "name": "name",
+            "type": "string"
+          },
+          {
+            "label": "Position",
+            "name": "position",
+            "type": "string"
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to content_types.json
+    Then the JSON response should be an array
+    And the JSON response should have 1 entry
+    And the JSON response at "0/order_by" should be "updated_at"
+    And the JSON response at "0/order_by_field_name" should be "updated_at"
+
+  Scenario: Creating Content Type with group_by_field_name
+    When I do an API POST to content_types.json with:
+    """
+    {
+      "content_type": {
+        "name": "Employees",
+        "slug": "employees",
+        "group_by_field_name": "category",
+        "entries_custom_fields": [
+          {
+            "label": "Name",
+            "name": "name",
+            "type": "string"
+          },
+          {
+            "label": "Category",
+            "name": "category",
+            "type": "select"
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to content_types.json
+    Then the JSON response should be an array
+    And the JSON response should have 1 entry
+    When I keep the JSON response at "0/entries_custom_fields/1/id" as "GROUP_BY_FIELD_ID"
+    Then the JSON response at "0/group_by_field_id" should be %{GROUP_BY_FIELD_ID}
+    And the JSON response at "0/group_by_field_name" should be "category"
+
+  Scenario: Creating Content Type with public_submission_account_emails
+    Given I have accounts:
+      | email         | id                        |
+      | user1@a.com   | 4f832c2cb0d86d3f42fffffc  |
+      | user2@a.com   | 4f832c2cb0d86d3f42fffffd  |
+      | user3@a.com   | 4f832c2cb0d86d3f42fffffe  |
+    When I do an API POST to content_types.json with:
+    """
+    {
+      "content_type": {
+        "name": "Employees",
+        "slug": "employees",
+        "entries_custom_fields": [
+          {
+            "label": "Name",
+            "name": "name",
+            "type": "string"
+          }
+        ],
+        "public_submission_enabled": true,
+        "public_submission_account_emails": [ "user1@a.com", "user2@a.com" ]
+      }
+    }
+    """
+    When I do an API GET request to content_types.json
+    Then the JSON response should be an array
+    And the JSON response should have 1 entry
+    And the JSON response at "0/public_submission_account_emails/0" should be "user1@a.com"
+    And the JSON response at "0/public_submission_account_emails/1" should be "user2@a.com"
+
+  Scenario: Creating Content Type with invalid public_submission_account_emails
+    Given I have accounts:
+      | email         | id                        |
+      | user1@a.com   | 4f832c2cb0d86d3f42fffffc  |
+    When I do an API POST to content_types.json with:
+    """
+    {
+      "content_type": {
+        "name": "Employees",
+        "slug": "employees",
+        "entries_custom_fields": [
+          {
+            "label": "Name",
+            "name": "name",
+            "type": "string"
+          }
+        ],
+        "public_submission_enabled": true,
+        "public_submission_account_emails": [ "user1@a.com", "user2@a.com" ]
+      }
+    }
+    """
+    When I do an API GET request to content_types.json
+    Then the JSON response should be an array
+    And the JSON response should have 1 entry
+    And the JSON response at "0/public_submission_account_emails" should be an array
+    And the JSON response at "0/public_submission_account_emails" should have 1 entry
+    And the JSON response at "0/public_submission_account_emails/0" should be "user1@a.com"

data/features/api/editable_elements.feature

@@ -0,0 +1,190 @@
+Feature: Editable Elements
+  In order to manage editable elements programmatically
+  As an API user
+  I will be able to create and update editable elements
+
+  Background:
+    Given I have the site: "test site" set up
+    And I have an "admin" API token
+    And a page named "hello-world" with id "4f832c2cb0d86d3f42fffffe" and template:
+    """
+    {% editable_long_text welcome %}
+    Welcome to my site!
+    {% endeditable_long_text %}
+
+    {% block main %}
+    {% editable_short_text subtitle %}
+    Article #1
+    {% endeditable_short_text %}
+    {% endblock %}
+    """
+
+  Scenario: Update editable element content
+    When I do an API GET request to pages/4f832c2cb0d86d3f42fffffe.json
+    Then I keep the JSON response at "editable_elements/0/id" as "LONG_TEXT_ID"
+    And I keep the JSON response at "editable_elements/1/id" as "SHORT_TEXT_ID"
+    When I do an API PUT to pages/4f832c2cb0d86d3f42fffffe.json with:
+    """
+    {
+      "page": {
+        "editable_elements": [
+          {
+            "slug": "welcome",
+            "block": null,
+            "content": "My new welcome content!!!"
+          },
+          {
+            "slug": "subtitle",
+            "block": "main",
+            "content": "My new main content!!!"
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to pages/4f832c2cb0d86d3f42fffffe.json
+    Then the JSON response at "editable_elements" should have 2 entries
+    And the JSON response at "editable_elements/0/content" should be "My new welcome content!!!"
+    And the JSON response at "editable_elements/1/content" should be "My new main content!!!"
+
+  Scenario: Create new editable element on existing page
+    When I do an API PUT to pages/4f832c2cb0d86d3f42fffffe.json with:
+    """
+    {
+      "page": {
+        "raw_template": "{% editable_short_text my_short_text %}{% endeditable_short_text %} {% block main %}{% editable_long_text my_long_text %}{% endeditable_long_text %}{% endblock %}",
+        "editable_elements": [
+          {
+            "slug": "my_short_text",
+            "block": null,
+            "content": "The new short text content"
+          },
+          {
+            "slug": "my_long_text",
+            "block": "main",
+            "content": "<p>The new long text content</p>"
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to pages/4f832c2cb0d86d3f42fffffe.json
+    Then the JSON response at "editable_elements" should have 2 entries
+    And the JSON response should have the following:
+      | editable_elements/0/slug    | "my_short_text"                       |
+      | editable_elements/0/block   | null                                  |
+      | editable_elements/0/content | "The new short text content"          |
+      | editable_elements/1/slug    | "my_long_text"                        |
+      | editable_elements/1/block   | "main"                                |
+      | editable_elements/1/content | "<p>The new long text content</p>"    |
+
+  Scenario: Create new editable element on new page
+    When I do an API POST to pages.json with:
+    """
+    {
+      "page": {
+        "title": "New Page",
+        "parent_fullpath": "index",
+        "raw_template": "{% editable_short_text my_short_text %}{% endeditable_short_text %} {% block main %}{% editable_long_text my_long_text %}{% endeditable_long_text %}{% endblock %}",
+        "editable_elements": [
+          {
+            "slug": "my_short_text",
+            "block": null,
+            "content": "The new short text content"
+          },
+          {
+            "slug": "my_long_text",
+            "block": "main",
+            "content": "<p>The new long text content</p>"
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to pages.json
+    Then the JSON response at "3/editable_elements" should have 2 entries
+    And the JSON response should have the following:
+      | 3/editable_elements/0/slug      | "my_short_text"                       |
+      | 3/editable_elements/0/block     | null                                  |
+      | 3/editable_elements/0/content   | "The new short text content"          |
+      | 3/editable_elements/1/slug      | "my_long_text"                        |
+      | 3/editable_elements/1/block     | "main"                                |
+      | 3/editable_elements/1/content   | "<p>The new long text content</p>"    |
+
+  Scenario: Create new editable file on new page
+    Given the JSON request at "page/editable_elements/0/source" is a file
+    When I do an API POST to pages.json with:
+    """
+    {
+      "page": {
+        "title": "New Page",
+        "parent_fullpath": "index",
+        "raw_template": "{% block main %}{% editable_file my_file %}{% endeditable_file %}{% endblock %}",
+        "editable_elements": [
+          {
+            "slug": "my_file",
+            "block": "main",
+            "source": "images/logo2.jpg"
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to pages.json
+    Then the JSON response at "3/editable_elements" should have 1 entry
+    And the JSON response should have the following:
+      | 3/editable_elements/0/slug      | "my_file"     |
+      | 3/editable_elements/0/block     | "main"        |
+    And the JSON at "3/editable_elements/0/url" should match /logo2.jpg$/
+
+  Scenario: Create new editable file on existing page
+    Given the JSON request at "page/editable_elements/0/source" is a file
+    When I do an API PUT to pages/4f832c2cb0d86d3f42fffffe.json with:
+    """
+    {
+      "page": {
+        "title": "New Page",
+        "parent_fullpath": "index",
+        "raw_template": "{% block main %}{% editable_file my_file %}{% endeditable_file %}{% endblock %}",
+        "editable_elements": [
+          {
+            "slug": "my_file",
+            "block": "main",
+            "source": "images/logo2.jpg"
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to pages/4f832c2cb0d86d3f42fffffe.json
+    Then the JSON response at "editable_elements" should have 1 entry
+    And the JSON response should have the following:
+      | editable_elements/0/slug    | "my_file"     |
+      | editable_elements/0/block   | "main"        |
+    And the JSON at "editable_elements/0/url" should match /logo2.jpg$/
+
+  Scenario: Create new editable file with no block
+    Given the JSON request at "page/editable_elements/0/source" is a file
+    When I do an API PUT to pages/4f832c2cb0d86d3f42fffffe.json with:
+    """
+    {
+      "page": {
+        "title": "New Page",
+        "parent_fullpath": "index",
+        "raw_template": "{% editable_file my_file %}{% endeditable_file %}",
+        "editable_elements": [
+          {
+            "slug": "my_file",
+            "block": null,
+            "source": "images/logo2.jpg"
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to pages/4f832c2cb0d86d3f42fffffe.json
+    Then the JSON response at "editable_elements" should have 1 entry
+    And the JSON response should have the following:
+      | editable_elements/0/slug    | "my_file"     |
+      | editable_elements/0/block   | null          |
+    And the JSON at "editable_elements/0/url" should match /logo2.jpg$/

data/features/api/entries_custom_fields.feature

@@ -0,0 +1,150 @@
+Feature: Entries Custom Field
+  In order to manage custom fields programmatically
+  As an API user
+  I will be able to create and update editable elements
+
+  Background:
+    Given I have the site: "test site" set up
+    And I have an "admin" API token
+    And I have a custom model named "Projects" with id "4f832c2cb0d86d3f42fffffe" and
+      | label       | type      | required        |
+      | Name        | string    | true            |
+      | Description | text      | false           |
+
+
+  Scenario: Return the minimal set of attributes for each kind of field
+    When I do an API GET request to content_types/4f832c2cb0d86d3f42fffffe.json
+    Then the JSON at "entries_custom_fields/0" should have 8 keys
+    Then the JSON at "entries_custom_fields/1" should have 9 keys
+
+  Scenario: Update custom field
+    When I do an API PUT to content_types/4f832c2cb0d86d3f42fffffe.json with:
+    """
+    {
+      "content_type": {
+        "entries_custom_fields": [
+          {
+            "name": "name",
+            "label": "Super cool name"
+          },
+          {
+            "name": "description",
+            "label": "Super cool description"
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to content_types/4f832c2cb0d86d3f42fffffe.json
+    Then the JSON response at "entries_custom_fields" should have 2 entries
+    And the JSON response at "entries_custom_fields/0/label" should be "Super cool name"
+    And the JSON response at "entries_custom_fields/1/label" should be "Super cool description"
+
+  Scenario: Delete a custom field
+    When I do an API PUT to content_types/4f832c2cb0d86d3f42fffffe.json with:
+    """
+    {
+      "content_type": {
+        "entries_custom_fields": [
+          {
+            "name": "name",
+            "label": "Super cool name"
+          },
+          {
+            "name": "description",
+            "_destroy": true
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to content_types/4f832c2cb0d86d3f42fffffe.json
+    Then the JSON response at "entries_custom_fields" should have 1 entry
+    And the JSON response at "entries_custom_fields/0/label" should be "Super cool name"
+
+  Scenario: Create new custom fields for existing content type
+    When I do an API PUT to content_types/4f832c2cb0d86d3f42fffffe.json with:
+    """
+    {
+      "content_type": {
+        "entries_custom_fields": [
+          {
+            "label": "Title",
+            "type": "string"
+          },
+          {
+            "label": "Content",
+            "type": "text"
+          },
+          {
+            "label": "Category",
+            "type": "select",
+            "select_options": [
+              {
+                "position": 1,
+                "name": {
+                  "en": "category1 (EN)",
+                  "fr": "category1 (FR)"
+                }
+              },
+              {
+                "position": 2,
+                "name": {
+                  "en": "category2 (EN)",
+                  "fr": "category2 (FR)"
+                }
+              }
+            ]
+          }
+        ]
+      }
+    }
+    """
+    When I do an API GET request to content_types/4f832c2cb0d86d3f42fffffe.json
+    Then the JSON response at "entries_custom_fields" should have 5 entries
+    And the JSON response should have the following:
+      | entries_custom_fields/2/label                         | "Title"           |
+      | entries_custom_fields/2/type                          | "string"          |
+      | entries_custom_fields/3/label                         | "Content"         |
+      | entries_custom_fields/3/type                          | "text"            |
+      | entries_custom_fields/4/label                         | "Category"        |
+      | entries_custom_fields/4/type                          | "select"          |
+      | entries_custom_fields/4/select_options/0/name         | "category1 (EN)"  |
+      | entries_custom_fields/4/select_options/1/name         | "category2 (EN)"  |
+      | entries_custom_fields/4/raw_select_options/0/name/fr  | "category1 (FR)"  |
+
+  Scenario: Create new custom field on new content type
+    When I do an API GET request to content_types.json
+    When I do an API POST to content_types.json with:
+    """
+    {
+      "content_type": {
+        "name": "My New Content Type",
+        "entries_custom_fields": [
+          {
+            "label": "Title",
+            "type": "string"
+          },
+          {
+            "label": "Content",
+            "type": "text"
+          },
+          {
+            "label": "Project",
+            "type": "belongs_to",
+            "class_name": "projects"
+          }
+        ]
+      }
+    }
+    """
+    Then the JSON response at "entries_custom_fields" should have 3 entries
+    And the JSON response should have the following:
+      | entries_custom_fields/0/label       | "Title"                                             |
+      | entries_custom_fields/0/type        | "string"                                            |
+      | entries_custom_fields/1/label       | "Content"                                           |
+      | entries_custom_fields/1/type        | "text"                                              |
+      | entries_custom_fields/2/label       | "Project"                                           |
+      | entries_custom_fields/2/type        | "belongs_to"                                        |
+      | entries_custom_fields/2/class_name  | "Locomotive::ContentEntry4f832c2cb0d86d3f42fffffe"  |
+      | entries_custom_fields/2/class_slug  | "projects"                                          |