Skip to content

Commit a460c13

Browse files
committed
docs: v0.8.5
1 parent 04d0d8d commit a460c13

File tree

2 files changed

+21
-0
lines changed

2 files changed

+21
-0
lines changed

README.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
1+
# Docker env
2+
3+
> Just one command to build all env for the easy-php
4+
5+
[![easy-env](https://asciinema.org/a/219911.svg)](https://asciinema.org/a/219911?autoplay=1)
6+
17
# How to build a PHP framework by ourself ?
28

39
Why do we need to build a PHP framework by ourself? Maybe the most of people will say "There have so many PHP frameworks be provided, but we still made a wheel?". My point is "Made a wheel is not our purpose, we will get a few of knowledge when making a wheel which is our really purpose".
@@ -869,6 +875,10 @@ project address: [https://github.com/TIGERB/easy-php](https://github.com/TIGERB/
869875

870876
# DONE
871877

878+
- v0.8.5(2018/01/06)
879+
- fix error_report
880+
- fix when __coreError is occur the response is output 200 but it also out put __coreError
881+
872882
- v0.8.1(2017/06/24)
873883
- use easy log
874884
- add folder bin

zh-cn/README.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,10 @@
1+
# Docker 环境
2+
3+
> 一行命令构建所有开发环境依赖
4+
5+
[![easy-env](https://asciinema.org/a/219911.svg)](https://asciinema.org/a/219911?autoplay=1)
6+
7+
18
# 如何构建一个自己的PHP框架
29

310
为什么我们要去构建一个自己的PHP框架?可能绝大多数的人都会说“市面上已经那么多的框架了,还造什么轮子?”。我的观点“造轮子不是目的,造轮子的过程中汲取到知识才是目的”。
@@ -876,6 +883,10 @@ cp ./.git-hooks/* ./git/hooks
876883

877884
# DONE
878885

886+
- v0.8.5(2018/01/06)
887+
- 使用error_report并设置为0,使得错误统一由框架的错误handle处理
888+
- 修复当__coreError发生时,会把__coreError和正常返回值同事输出的问题
889+
879890
- v0.8.1(2018/06/24)
880891
- 重构日志类
881892
- 增加bin目录统一存放脚本文件

0 commit comments

Comments
 (0)