dyweb / bmfu Goto Github PK

Because i have changed ci's database class, so it will throw Exception when having unit test.
But this wont happen in production and development environment. so i have to add another check
for create and update error (eg: column doesn't exist).

may set the environment to test in different mode. (database class has/not exception)

• not found
• authorize
• validation error

• before create
• after create
• before update
• after update
• before delete
• after delete

and we may need to use event emitter, we can use symphony's ?

I wrote a style guide in https://github.com/dyweb/bmFu/blob/master/doc/style.md

but now seems we have bifurcated.

@arrowrowe use countAll for model methods instead of count_all

I think it's still not too late to have this discussion.

Advantage of snake_case

1. it follows the old standard in Codeignitor based project
2. it's more explicit than camelCase

Advantage of CamelCase

1. it follows modern php standard

@arrowrowe @ComMouse @swaylq @xsfour

so let's have a vote, 👍 for snake_case, 👎 for camelCase

1. generate standard output for validation error
2. return 400 because it is client error.
3. better have angularjs integration so front end will have little work to do. we can extend $http to another service.

you can use ilex's, but i suggest consider the one used in laravel in axws and the current one we are using in tongqu's tq folder, the one in dywiki is the newer version for that.

currently we are using 'dev-master' and it's better to have version number and we can install using zip.

• hard delete
• soft delete

use trait?

• usage in README.md and project wiki
• add a MIT license to project.
• comment for some core code.

And a Chinese version readme.....

1. in memory cache.

eg: $row1 = User::find(1) ->
SELECT * FROMuserWHEREid= 1
User::$cached_rows['1'] = $row1 // then we cache
$row2 = User::find(1) -> return $cached_rows[1] // no more queries

2. in redis cache

eg: user A $act = Act::find(1) dbquery, $redis_client->set('user/1',$user)
user B $act = Act::find(1) $redis_client->get('user/1')

3. in mysql cache

eg: analysis for user like and dislike, friends etc. (table is large and these wont change very often)

the at15/restful may have the implementation ( have a look at `src/Dy/Restful/Resource

because bmfu can be mounted to controller directly. they should get the user input and give correct
response. even if the request is invalid or contain injection.

laravel's TestCase can use $this->call to use http methods. we can learn from them.

just for convenient, so we can catch it in the router

Do we need to deal with relation tables & join staff? If yes, we need to extend the model to support it. @at15 @swaylq @arrowrowe @xsfour

• selected fields eg: act?select=name,desc,create_time
• order by eg: act?order=+create_time-member_count
• where eg: act?type=1

allow using the model to filter the user input, instead of write it in every controller

• support user input see #2
• provide count.

not all table need these two columns, eg: notification table doesn't need update_time.

add some method or const in order to enable/disable it when create and update

Do we need to realize it? If yes, then

• Just use to iterate the objects (array wrapper)?
• Also used in insert_batch, update_batch?

Needs further discussion.

https://ocramius.github.io/ProxyManager/docs/lazy-loading-value-holder.html

this might fix all the boot methods before every method call