Magetwo 84934 fix bluefoot advance slider alignment

.gitignore

@@ -0,0 +1,11 @@
+.idea
+dev/build/
+/var/*
+**/node_modules/*
+/robo.yml
+/vendor/
+/.requirejs-config.js
+/.path-mapping.json
+/jest.config.json
+**.js.map
+**.d.js

NEW_REPOSITORY.md

@@ -0,0 +1,79 @@
+# Development in new repository structure
+
+### Development Installation
+
+1. Install all dependencies
+    ```bash
+    composer install && yarn install
+    ```
+
+2. Configure robo (docker or local mysql):
+
+    **Docker mysql** (make sure container has either port or ip address accessible to host)
+    ```bash
+    vendor/bin/robo build:configuration-from-docker-container [name of mysql container]
+    ```
+
+    **Local mysql**
+    ```bash
+    vendor/bin/robo build:configuration [mysql host] [mysql username] [mysql password]
+    ```
+
+
+### Running Tests
+
+Before running any tests, you need to create a development build
+
+```bash
+vendor/bin/robo build:create dev [your prefered url] [magento branch of current story]
+```
+
+#### JavaScript Tests
+
+##### Command Line
+To run a complete suite you can just execute this simple command
+
+```bash
+npx jest --no-cache
+```
+
+If you want to execute a separate test file, just specify its path
+
+```bash
+npx jest [path-to-file]
+```
+
+##### PHPStorm Integration
+
+1. Enable Node & NPM integration in **PHPStorm > Preferences > Language & Frameworks > NodeJs & NPM > Enable**
+
+2. Before you can run any javascript tests you need to export jest configuration file for PHPStorm.
+```
+npx gulp jestConfig
+```
+
+3. Then you have specify jest.config.json in **PHPStorm > Run > Edit Configurations > Defaults -> Jest:**
+
+    - Select your jest.config.json into **Configuration File** file
+
+    - Specify your repo directory in **Working directory** field
+
+    - Specify your "--no-cache" into **Jest options** field
+
+    - Node runtime & jest executable should be automatically pre-filled
+
+Now you can just right click on any JS test file and run them in your IDE.
+
+#### Functional Tests
+
+As soon as your build is accessible via specified url in `build:create` command
+
+```bash
+vendor/bin/robo run:functional-test --build [buildname]
+```
+
+You can also execute tests byt name
+
+```bash
+vendor/bin/robo run:functional-test --build [buildname] --test-name [NameOfTestCest]
+```

README.md

@@ -1,2 +1,105 @@
-# bluefoot
-Bluefoot Extension
+# BlueFoot Magento 2 module
+The BlueFoot module provides drag & drop content building functionality to Magento 2. Originally produced by Gene Commerce and acquired at the start of 2017 by Magento.
+
+### Development Installation
+
+You will need to have Magento EE running alongside having this repository symlinked into your installation.
+
+#### Installing Magento 2 EE
+
+You need to run the following commands to install Magento EE:
+
+- Clone the CE & EE repositories
+- Run the `build-ee.php` script to create symlinks from the EE repository within the CE repository
+- Copy over the EE composer.json file into the CE repository
+- Remove the composer.lock file
+- Install composer dependencies
+
+```bash
+git clone [email protected]:magento-obsessive-owls/magento2ce.git
+git clone [email protected]:magento-obsessive-owls/magento2ee.git
+php magento2ee/dev/tools/build-ee.php
+cp magento2ee/composer.json magento2ce/
+rm -rf magento2ce/composer.lock
+cd magento2ce
+composer install
+```
+
+You will then be working out of the `magento2ce` repository, this repository will be running EE code of the latest version available.
+
+#### Installing BlueFoot
+
+In the same directory you ran the above commands you will need to run the following:
+
+```bash
+git clone [email protected]:magento-obsessive-owls/bluefoot.git
+mkdir magento2ce/app/code/Gene/
+cd magento2ce/app/code/Gene/
+ln -s ../../../../bluefoot/app/code/Gene/BlueFoot/ BlueFoot
+```
+
+This will symlink the module within `bluefoot` folder to your EE.
+
+#### Linking Functional Acceptence Tests
+The tests live in the core of our module and will need to be linked into your `magento2ce` project. This assumes you've already installed the acceptence framework within your installation.
+
+> Installation of the framework is as simple as navigating to `dev/tests/acceptence` then running `composer install`
+
+To link the acceptence tests you simply need to run the following commands from the root of the `magento2ce` folder:
+
+```bash
+cd dev/tests/acceptance/tests/functional/Magento/FunctionalTest/
+ln -s ../../../../../../../../bluefoot/dev/tests/acceptance/tests/functional/Magento/FunctionalTest/BlueFoot/ BlueFoot
+```
+
+The tests will then be available your Magento installation for running with MFTF.
+
+#### Resolving Template Validation Issues
+
+You need to replace the paths that the system tries to load template files from to stop Magento throwing an invalid path error for the EE & BlueFoot templates.
+
+Open `magento2ce/lib/internal/Magento/Framework/Component/ComponentRegistrar.php` and modify the `render` function to replace the new paths with the `magento2ce` path like below.
+
+```Php
+    /**
+     * Sets the location of a component.
+     *
+     * @param string $type component type
+     * @param string $componentName Fully-qualified component name
+     * @param string $path Absolute file path to the component
+     * @throws \LogicException
+     * @return void
+     */
+    public static function register($type, $componentName, $path)
+    {
+        $path = str_replace(['magento2ee', 'bluefoot'], 'magento2ce', $path);
+
+        self::validateType($type);
+        if (isset(self::$paths[$type][$componentName])) {
+            throw new \LogicException(
+                ucfirst($type) . ' \'' . $componentName . '\' from \'' . $path . '\' '
+                . 'has been already defined in \'' . self::$paths[$type][$componentName] . '\'.'
+            );
+        } else {
+            self::$paths[$type][$componentName] = str_replace('\\', '/', $path);
+        }
+    }
+```
+
+Note: the addition here is the `str_replace` which is converting the file paths to resolve always to the `magento2ce` directory.
+
+```php
+$path = str_replace(['magento2ee', 'bluefoot'], 'magento2ce', $path);
+```
+
+#### Run Setup
+
+Finally you'll need to run the Magento 2 setup upgrade command to perform any migrations & installation scripts of the module.
+
+```bash
+bin/magento setup:upgrade
+```
+
+### Usage
+
+BlueFoot appears in areas where the TinyMCE WYSWIYG was previously available. You can validate if BlueFoot is working by an additional button to `Activate Advanced CMS` being placed above the WYSIWYG instance. 

RoboFile.php

@@ -0,0 +1,22 @@
+<?php
+/**
+ * Copyright © Magento, Inc. All rights reserved.
+ * See COPYING.txt for license details.
+ */
+
+/**
+ * Robo tasks container
+ *
+ */
+class RoboFile extends \Robo\Tasks
+{
+    use Magento\RoboFile\loadTasks;
+
+    /**
+     * Sets root project directory for dev tasks
+     */
+    public function __construct()
+    {
+        $this->projectRoot = __DIR__;
+    }
+}

app/code/Gene/BlueFoot/.gitignore

@@ -0,0 +1,8 @@
+config.codekit
+.idea
+node_modules
+view/adminhtml/coverage
+view/adminhtml/web/es6
+view/adminhtml/web/css/magento2.css
+
+package-lock\.json

app/code/Gene/BlueFoot/Api/AttributeGroupRepositoryInterface.php

@@ -0,0 +1,54 @@
+<?php
+
+namespace Gene\BlueFoot\Api;
+
+/**
+ * Interface AttributeGroupRepositoryInterface
+ *
+ * @package Gene\BlueFoot\Api
+ *
+ * @author Dave Macaulay <[email protected]>
+ */
+interface AttributeGroupRepositoryInterface
+{
+    /**
+     * Save attribute group
+     *
+     * @param \Magento\Eav\Api\Data\AttributeGroupInterface $group
+     * @return \Magento\Eav\Api\Data\AttributeGroupInterface
+     */
+    public function save(\Magento\Eav\Api\Data\AttributeGroupInterface $group);
+
+    /**
+     * Retrieve list of attribute groups
+     *
+     * @param \Magento\Framework\Api\SearchCriteriaInterface $searchCriteria
+     * @return \Magento\Eav\Api\Data\AttributeGroupSearchResultsInterface
+     * @throws \Magento\Framework\Exception\NoSuchEntityException
+     */
+    public function getList(\Magento\Framework\Api\SearchCriteriaInterface $searchCriteria);
+
+    /**
+     * Retrieve attribute group
+     *
+     * @param int $groupId
+     * @return \Magento\Eav\Api\Data\AttributeGroupInterface
+     */
+    public function get($groupId);
+
+    /**
+     * Remove attribute group
+     *
+     * @param \Magento\Eav\Api\Data\AttributeGroupInterface $group
+     * @return bool
+     */
+    public function delete(\Magento\Eav\Api\Data\AttributeGroupInterface $group);
+
+    /**
+     * Remove attribute group by id
+     *
+     * @param int $groupId
+     * @return bool
+     */
+    public function deleteById($groupId);
+}

app/code/Gene/BlueFoot/Api/AttributeRepositoryInterface.php

@@ -0,0 +1,61 @@
+<?php
+
+namespace Gene\BlueFoot\Api;
+
+/**
+ * Interface AttributeRepositoryInterface
+ *
+ * @package Magento\Catalog\Api
+ *
+ * @author Dave Macaulay <[email protected]>
+ */
+interface AttributeRepositoryInterface extends \Magento\Framework\Api\MetadataServiceInterface
+{
+    /**
+     * Retrieve all attributes for entity type
+     *
+     * @param \Magento\Framework\Api\SearchCriteriaInterface $searchCriteria
+     * @return \Magento\Catalog\Api\Data\ProductAttributeSearchResultsInterface
+     */
+    public function getList(\Magento\Framework\Api\SearchCriteriaInterface $searchCriteria);
+
+    /**
+     * Retrieve specific attribute
+     *
+     * @param string $attributeCode
+     * @return \Magento\Catalog\Api\Data\ProductAttributeInterface
+     * @throws \Magento\Framework\Exception\NoSuchEntityException
+     */
+    public function get($attributeCode);
+
+    /**
+     * Save attribute data
+     *
+     * @param \Magento\Catalog\Api\Data\ProductAttributeInterface $attribute
+     * @return \Magento\Catalog\Api\Data\ProductAttributeInterface
+     * @throws \Magento\Framework\Exception\NoSuchEntityException
+     * @throws \Magento\Framework\Exception\InputException
+     * @throws \Magento\Framework\Exception\StateException
+     */
+    public function save(\Magento\Catalog\Api\Data\ProductAttributeInterface $attribute);
+
+    /**
+     * Delete Attribute
+     *
+     * @param \Magento\Catalog\Api\Data\ProductAttributeInterface $attribute
+     * @return bool True if the entity was deleted (always true)
+     * @throws \Magento\Framework\Exception\StateException
+     * @throws \Magento\Framework\Exception\NoSuchEntityException
+     */
+    public function delete(\Magento\Catalog\Api\Data\ProductAttributeInterface $attribute);
+
+    /**
+     * Delete Attribute by id
+     *
+     * @param string $attributeCode
+     * @return bool
+     * @throws \Magento\Framework\Exception\StateException
+     * @throws \Magento\Framework\Exception\NoSuchEntityException
+     */
+    public function deleteById($attributeCode);
+}