mirror/php-flarum
1
0
Fork 0
mirror of https://github.com/flarum/core.git synced 2025-08-01 14:10:37 +02:00
Code Issues Releases Wiki Activity

add links

tobscure
2014-12-19 21:37:35 -08:00
parent fc49e5b7a0
commit c7e8c4a743
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Architecture.md

@@ -14,7 +14,7 @@ Flarum is a dynamic application and its domain needs to be able to be extended w
**Entities** (e.g. Discussion, Post, User) are based on Laravel’s Eloquent ORM. They use [Permissible](https://github.com/tobscure/permissible) to define logical permission clauses. They also have inbuilt validation.
**Repositories** are generally used to find/save/delete entities, providing a proper layer of database abstraction. However, during development so far, adhering strictly to this pattern has sometimes caused more trouble than it is worth (especially when thinking about how [Extensions]() will deal with Entities and Repositories.) Thus, the abstraction is a bit leaky. This may become apparent and need to be dealt with when [tests are written]().
**Repositories** are generally used to find/save/delete entities, providing a proper layer of database abstraction. However, during development so far, adhering strictly to this pattern has sometimes caused more trouble than it is worth (especially when thinking about how [Extensions] will deal with Entities and Repositories.) Thus, the abstraction is a bit leaky. This may become apparent and need to be dealt with when [tests are written](https://github.com/flarum/core/issues/3).
**Commands** and **Domain Events** are associated with each Entity type, in line with [this pattern](https://github.com/laracasts/Commander). **Listeners** are used to do things like update metadata (post count, last post time, etc.), format post content, and send emails. This pattern is very suitable as Extensions will easily be able to listen for Domain Events.
@@ -30,4 +30,4 @@ Flarum's Ember.js application is built with [ember-cli](http://ember-cli.com), a
The web layer’s main responsibility is to render a page which includes these CSS/JS files, and then simply runs the Ember app. It manages assets so that Extensions will be able to add their own CSS/JS files to extend the Ember app.
In the future, the web layer will need to support routes and render basic content before bootstrapping the Ember app accordingly (#?).
In the future, the web layer will need to support routes and render basic content before bootstrapping the Ember app accordingly (#14).