From a0faab7290409666b5b92582ee94e9c3f45e4b0c Mon Sep 17 00:00:00 2001 From: Vadim Justus <v.justus@techdivision.com> Date: Sat, 2 Mar 2019 11:02:33 +0100 Subject: [PATCH] Update changelog log and readme file --- .gitignore | 2 ++ CHANGELOG.md | 22 ++++++++++++++++++++++ README.md | 29 +++++++---------------------- 3 files changed, 31 insertions(+), 22 deletions(-) create mode 100644 .gitignore create mode 100644 CHANGELOG.md diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..8e69e07 --- /dev/null +++ b/.gitignore @@ -0,0 +1,2 @@ +/.idea + diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100644 index 0000000..8302fb6 --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,22 @@ +# CHANGELOG + +## 1.0.3 +* *Bugfix:* Fix issue with missing `store_id` values while persisting block entries. + +## 1.0.2 +* *Bugfix:* Extend schema in order to allow `.` for `key` like it is shown in the examples + +## 1.0.1 +* *Bugfix:* Add PHP 7.1 compatibility + +## 1.0.0 +* *Feature:* Notification in Magento backend (admin), for editors - if the content entry is maintained by code +* *Improvement:* Introduce `key` attribute for configured entries, in order to improve merging of all configurations +* *Refactoring:* Improve query for fetching existing cms entities by configured entries + +## 0.1.0 +* *Feature:* Implement initial functionality +** Configuration for pages +** Configuration for blocks +** Recurring setup installer for pages +** Recurring setup installer for blocks \ No newline at end of file diff --git a/README.md b/README.md index bcc8160..2140914 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,6 @@ to database on each `setup:upgrade` run. ## Install with composer ```bash -composer config repositories.firegento.content-provisioning vcs https://github.com/magento-hackathon/m2-content-provisioning.git composer require firegento/magento2-content-provisioning ``` @@ -119,24 +118,10 @@ This node is optional. If it is not defined, the block or page will be applied t will also be applied to stores, which will be created in the future after re-running `setup:upgrade` command. You can also use the 'wildcard' `*` in order to define that the content should be applied to all stores. -## Planed features / Road map -| Status | Feature/Change | Version | -|---|---|---| -| planned | Refactoring: Needs to find a pretty solution in order avoid some duplicate code... | 1.1.x | -| planned | CLI command to apply dedicated configured content entries to database | 1.2.x | -| planned | Integration tests | 1.2.x | -| idea | Add a button to page or block edit page in Magento backend, if there is content defined for this page in code. (Like: "Use default content") | ? | -| idea | Persist version hash every time the content is applied to database and track whether is was changes by editor. (Auto `maintained` mode) | ? | - -Further ideas are welcome :) - -## Major changes -| Feature/Change | Version | -|---|---| -| Configuration for pages | 0.1.0 | -| Configuration for blocks | 0.1.0 | -| Recurring setup installer for pages | 0.1.0 | -| Recurring setup installer for blocks | 0.1.0 | -| Notification in Magento backend (admin), for editors - if the content entry is maintained by code | 1.0.0 | -| Introduce `key` attribute for configured entries, in order to improve merging of all configurations | 1.0.0 | -| Refactoring: Improve query for fetching existing cms entities by configured entries | 1.0.0 | +## Issues and planned features +See issues to see what's planed next: https://github.com/magento-hackathon/m2-content-provisioning/issues +Feel free to add your ideas there. + +## Changelog +See [changelog file](CHANGELOG.md) + \ No newline at end of file -- GitLab