2015-08-27 07:40:18 +08:00
|
|
|
<?php
|
2016-11-29 13:03:53 +08:00
|
|
|
|
2015-08-26 14:48:58 +08:00
|
|
|
/*
|
|
|
|
* This file is part of Flarum.
|
|
|
|
*
|
|
|
|
* (c) Toby Zerner <toby.zerner@gmail.com>
|
|
|
|
*
|
|
|
|
* For the full copyright and license information, please view the LICENSE
|
|
|
|
* file that was distributed with this source code.
|
|
|
|
*/
|
|
|
|
|
2017-06-24 19:43:33 +08:00
|
|
|
namespace Flarum\Post;
|
2015-07-04 10:54:48 +08:00
|
|
|
|
2016-02-10 18:00:37 +08:00
|
|
|
use Flarum\Database\AbstractModel;
|
Overhaul model visibility scoping (#1342)
* Overhaul the way model visibility scoping works
- Previously post visibility scoping required concrete knowledge of the
parent discussion, ie. you needed a Discussion model on which you
would call `postsVisibleTo($actor)`. This meant that to fetch posts
from different discussions (eg. when listing user posts), it was a
convoluted process, ultimately causing #1333.
Now posts behave like any other model in terms of visibility scoping,
and you simply call `whereVisibleTo($actor)` on a Post query. This
scope will automatically apply a WHERE EXISTS clause that scopes the
query to only include posts whose discussions are visible too. Thus,
fetching posts from multiple discussions can now be done in a single
query, simplifying things greatly and fixing #1333.
- As such, the ScopePostVisibility event has been removed. Also, the
rest of the "Scope" events have been consolidated into a single event,
ScopeModelVisibility. This event is called whenever a user must have
a certain $ability in order to see a set of discussions. Typically
this ability is just "view". But in the case of discussions which have
been marked as `is_private`, it is "viewPrivate". And in the case of
discussions which have been hidden, it is "hide". etc.
The relevant API on AbstractPolicy has been refined, now providing
`find`, `findPrivate`, `findEmpty`, and `findWithPermission` methods.
This could probably do with further refinement and we can re-address
it once we get around to implementing more Extenders.
- An additional change is that Discussion::comments() (the relation
used to calculate the cached number of replies) now yields "comments
that are not private", where before it meant "comments that are
visible to Guests". This was flawed because eg. comments in non-public
tags are technically not visible to Guests.
Consequently, the Approval extension must adopt usage of `is_private`,
so that posts which are not approved are not included in the replies
count. Fundamentally, `is_private` now indicates that a discussion/
post should be hidden by default and should only be visible if it
meets certain criteria. This is in comparison to non-is_private
entities, which are visible by default and may be hidden if they don't
meet certain criteria.
Note that these changes have not been extensively tested, but I have
been over the logic multiple times and it seems to check out.
* Add event to determine whether a discussion `is_private`
See https://github.com/flarum/core/pull/1153#issuecomment-292693624
* Don't include hidden posts in the comments count
* Apply fixes from StyleCI (#1350)
2018-01-27 07:27:16 +08:00
|
|
|
use Flarum\Discussion\Discussion;
|
|
|
|
use Flarum\Event\GetModelIsPrivate;
|
|
|
|
use Flarum\Event\ScopeModelVisibility;
|
2017-06-24 21:48:20 +08:00
|
|
|
use Flarum\Foundation\EventGeneratorTrait;
|
2017-06-24 19:43:33 +08:00
|
|
|
use Flarum\Post\Event\Deleted;
|
2017-06-24 21:04:46 +08:00
|
|
|
use Flarum\User\User;
|
2015-07-04 10:54:48 +08:00
|
|
|
use Illuminate\Database\Eloquent\Builder;
|
|
|
|
|
2015-07-07 17:50:18 +08:00
|
|
|
/**
|
Major refactor and improvements
- Reorganised all namespaces and class names for consistency and structure. Following PSR bylaws (Abstract prefix, Interface/Trait suffix).
- Move models into root of Core, because writing `use Flarum\Core\Discussion` is nice. Namespace the rest by type. (Namespacing by entity was too arbitrary.)
- Moved some non-domain stuff out of Core: Database, Formatter, Settings.
- Renamed config table and all references to "settings" for consistency.
- Remove Core class and add url()/isInstalled()/inDebugMode() as instance methods of Foundation\Application.
- Cleanup, docblocking, etc.
- Improvements to HTTP architecture
- API and forum/admin Actions are now actually all the same thing (simple PSR-7 Request handlers), renamed to Controllers.
- Upgrade to tobscure/json-api 0.2 branch.
- Where possible, moved generic functionality to tobscure/json-api (e.g. pagination links). I'm quite happy with the backend balance now re: #262
- Improvements to other architecture
- Use Illuminate's Auth\Access\Gate interface/implementation instead of our old Locked trait. We still use events to actually determine the permissions though. Our Policy classes are actually glorified event subscribers.
- Extract model validation into Core\Validator classes.
- Make post visibility permission stuff much more efficient and DRY.
- Renamed Flarum\Event classes for consistency. ref #246
- `Configure` prefix for events dedicated to configuring an object.
- `Get` prefix for events whose listeners should return something.
- `Prepare` prefix when a variable is passed by reference so it can be modified.
- `Scope` prefix when a query builder is passed.
- Miscellaneous improvements/bug-fixes. I'm easily distracted!
- Increase default height of post composer.
- Improve post stream redraw flickering in Safari by keying loading post placeholders with their IDs. ref #451
- Use a PHP JavaScript minification library for minifying TextFormatter's JavaScript, instead of ClosureCompilerService (can't rely on external service!)
- Use UrlGenerator properly in various places. closes #123
- Make Api\Client return Response object. closes #128
- Allow extensions to specify custom icon images.
- Allow external API/admin URLs to be optionally specified in config.php. If the value or "url" is an array, we look for the corresponding path inside. Otherwise, we append the path to the base URL, using the corresponding value in "paths" if present. closes #244
2015-10-08 11:58:02 +08:00
|
|
|
* @property int $id
|
|
|
|
* @property int $discussion_id
|
|
|
|
* @property int $number
|
|
|
|
* @property \Carbon\Carbon $time
|
|
|
|
* @property int|null $user_id
|
|
|
|
* @property string|null $type
|
|
|
|
* @property string|null $content
|
|
|
|
* @property \Carbon\Carbon|null $edit_time
|
|
|
|
* @property int|null $edit_user_id
|
|
|
|
* @property \Carbon\Carbon|null $hide_time
|
|
|
|
* @property int|null $hide_user_id
|
2017-06-24 19:48:04 +08:00
|
|
|
* @property \Flarum\Discussion\Discussion|null $discussion
|
Major refactor and improvements
- Reorganised all namespaces and class names for consistency and structure. Following PSR bylaws (Abstract prefix, Interface/Trait suffix).
- Move models into root of Core, because writing `use Flarum\Core\Discussion` is nice. Namespace the rest by type. (Namespacing by entity was too arbitrary.)
- Moved some non-domain stuff out of Core: Database, Formatter, Settings.
- Renamed config table and all references to "settings" for consistency.
- Remove Core class and add url()/isInstalled()/inDebugMode() as instance methods of Foundation\Application.
- Cleanup, docblocking, etc.
- Improvements to HTTP architecture
- API and forum/admin Actions are now actually all the same thing (simple PSR-7 Request handlers), renamed to Controllers.
- Upgrade to tobscure/json-api 0.2 branch.
- Where possible, moved generic functionality to tobscure/json-api (e.g. pagination links). I'm quite happy with the backend balance now re: #262
- Improvements to other architecture
- Use Illuminate's Auth\Access\Gate interface/implementation instead of our old Locked trait. We still use events to actually determine the permissions though. Our Policy classes are actually glorified event subscribers.
- Extract model validation into Core\Validator classes.
- Make post visibility permission stuff much more efficient and DRY.
- Renamed Flarum\Event classes for consistency. ref #246
- `Configure` prefix for events dedicated to configuring an object.
- `Get` prefix for events whose listeners should return something.
- `Prepare` prefix when a variable is passed by reference so it can be modified.
- `Scope` prefix when a query builder is passed.
- Miscellaneous improvements/bug-fixes. I'm easily distracted!
- Increase default height of post composer.
- Improve post stream redraw flickering in Safari by keying loading post placeholders with their IDs. ref #451
- Use a PHP JavaScript minification library for minifying TextFormatter's JavaScript, instead of ClosureCompilerService (can't rely on external service!)
- Use UrlGenerator properly in various places. closes #123
- Make Api\Client return Response object. closes #128
- Allow extensions to specify custom icon images.
- Allow external API/admin URLs to be optionally specified in config.php. If the value or "url" is an array, we look for the corresponding path inside. Otherwise, we append the path to the base URL, using the corresponding value in "paths" if present. closes #244
2015-10-08 11:58:02 +08:00
|
|
|
* @property User|null $user
|
|
|
|
* @property User|null $editUser
|
|
|
|
* @property User|null $hideUser
|
2015-12-23 20:54:58 +08:00
|
|
|
* @property string $ip_address
|
2017-05-27 12:49:15 +08:00
|
|
|
* @property bool $is_private
|
2015-07-07 17:50:18 +08:00
|
|
|
*/
|
Major refactor and improvements
- Reorganised all namespaces and class names for consistency and structure. Following PSR bylaws (Abstract prefix, Interface/Trait suffix).
- Move models into root of Core, because writing `use Flarum\Core\Discussion` is nice. Namespace the rest by type. (Namespacing by entity was too arbitrary.)
- Moved some non-domain stuff out of Core: Database, Formatter, Settings.
- Renamed config table and all references to "settings" for consistency.
- Remove Core class and add url()/isInstalled()/inDebugMode() as instance methods of Foundation\Application.
- Cleanup, docblocking, etc.
- Improvements to HTTP architecture
- API and forum/admin Actions are now actually all the same thing (simple PSR-7 Request handlers), renamed to Controllers.
- Upgrade to tobscure/json-api 0.2 branch.
- Where possible, moved generic functionality to tobscure/json-api (e.g. pagination links). I'm quite happy with the backend balance now re: #262
- Improvements to other architecture
- Use Illuminate's Auth\Access\Gate interface/implementation instead of our old Locked trait. We still use events to actually determine the permissions though. Our Policy classes are actually glorified event subscribers.
- Extract model validation into Core\Validator classes.
- Make post visibility permission stuff much more efficient and DRY.
- Renamed Flarum\Event classes for consistency. ref #246
- `Configure` prefix for events dedicated to configuring an object.
- `Get` prefix for events whose listeners should return something.
- `Prepare` prefix when a variable is passed by reference so it can be modified.
- `Scope` prefix when a query builder is passed.
- Miscellaneous improvements/bug-fixes. I'm easily distracted!
- Increase default height of post composer.
- Improve post stream redraw flickering in Safari by keying loading post placeholders with their IDs. ref #451
- Use a PHP JavaScript minification library for minifying TextFormatter's JavaScript, instead of ClosureCompilerService (can't rely on external service!)
- Use UrlGenerator properly in various places. closes #123
- Make Api\Client return Response object. closes #128
- Allow extensions to specify custom icon images.
- Allow external API/admin URLs to be optionally specified in config.php. If the value or "url" is an array, we look for the corresponding path inside. Otherwise, we append the path to the base URL, using the corresponding value in "paths" if present. closes #244
2015-10-08 11:58:02 +08:00
|
|
|
class Post extends AbstractModel
|
2015-07-04 10:54:48 +08:00
|
|
|
{
|
2017-06-24 19:33:42 +08:00
|
|
|
use EventGeneratorTrait;
|
2015-07-05 10:55:08 +08:00
|
|
|
|
|
|
|
/**
|
|
|
|
* {@inheritdoc}
|
|
|
|
*/
|
|
|
|
protected $table = 'posts';
|
2015-07-04 10:54:48 +08:00
|
|
|
|
|
|
|
/**
|
|
|
|
* {@inheritdoc}
|
|
|
|
*/
|
2015-07-18 21:29:47 +08:00
|
|
|
protected $dates = ['time', 'edit_time', 'hide_time'];
|
2015-07-04 10:54:48 +08:00
|
|
|
|
2017-05-27 12:49:15 +08:00
|
|
|
/**
|
|
|
|
* Casts properties to a specific type.
|
|
|
|
*
|
|
|
|
* @var array
|
|
|
|
*/
|
|
|
|
protected $casts = [
|
|
|
|
'is_private' => 'boolean'
|
|
|
|
];
|
|
|
|
|
2015-07-04 10:54:48 +08:00
|
|
|
/**
|
|
|
|
* A map of post types, as specified in the `type` column, to their
|
|
|
|
* classes.
|
|
|
|
*
|
|
|
|
* @var array
|
|
|
|
*/
|
|
|
|
protected static $models = [];
|
|
|
|
|
|
|
|
/**
|
|
|
|
* The type of post this is, to be stored in the posts table.
|
|
|
|
*
|
|
|
|
* Should be overwritten by subclasses with the value that is
|
|
|
|
* to be stored in the database, which will then be used for
|
|
|
|
* mapping the hydrated model instance to the proper subtype.
|
|
|
|
*
|
|
|
|
* @var string
|
|
|
|
*/
|
|
|
|
public static $type = '';
|
|
|
|
|
|
|
|
/**
|
|
|
|
* {@inheritdoc}
|
|
|
|
*/
|
|
|
|
public static function boot()
|
|
|
|
{
|
|
|
|
parent::boot();
|
|
|
|
|
|
|
|
// When a post is created, set its type according to the value of the
|
|
|
|
// subclass. Also give it an auto-incrementing number within the
|
|
|
|
// discussion.
|
|
|
|
static::creating(function (Post $post) {
|
|
|
|
$post->type = $post::$type;
|
|
|
|
$post->number = ++$post->discussion->number_index;
|
|
|
|
$post->discussion->save();
|
|
|
|
});
|
|
|
|
|
Overhaul model visibility scoping (#1342)
* Overhaul the way model visibility scoping works
- Previously post visibility scoping required concrete knowledge of the
parent discussion, ie. you needed a Discussion model on which you
would call `postsVisibleTo($actor)`. This meant that to fetch posts
from different discussions (eg. when listing user posts), it was a
convoluted process, ultimately causing #1333.
Now posts behave like any other model in terms of visibility scoping,
and you simply call `whereVisibleTo($actor)` on a Post query. This
scope will automatically apply a WHERE EXISTS clause that scopes the
query to only include posts whose discussions are visible too. Thus,
fetching posts from multiple discussions can now be done in a single
query, simplifying things greatly and fixing #1333.
- As such, the ScopePostVisibility event has been removed. Also, the
rest of the "Scope" events have been consolidated into a single event,
ScopeModelVisibility. This event is called whenever a user must have
a certain $ability in order to see a set of discussions. Typically
this ability is just "view". But in the case of discussions which have
been marked as `is_private`, it is "viewPrivate". And in the case of
discussions which have been hidden, it is "hide". etc.
The relevant API on AbstractPolicy has been refined, now providing
`find`, `findPrivate`, `findEmpty`, and `findWithPermission` methods.
This could probably do with further refinement and we can re-address
it once we get around to implementing more Extenders.
- An additional change is that Discussion::comments() (the relation
used to calculate the cached number of replies) now yields "comments
that are not private", where before it meant "comments that are
visible to Guests". This was flawed because eg. comments in non-public
tags are technically not visible to Guests.
Consequently, the Approval extension must adopt usage of `is_private`,
so that posts which are not approved are not included in the replies
count. Fundamentally, `is_private` now indicates that a discussion/
post should be hidden by default and should only be visible if it
meets certain criteria. This is in comparison to non-is_private
entities, which are visible by default and may be hidden if they don't
meet certain criteria.
Note that these changes have not been extensively tested, but I have
been over the logic multiple times and it seems to check out.
* Add event to determine whether a discussion `is_private`
See https://github.com/flarum/core/pull/1153#issuecomment-292693624
* Don't include hidden posts in the comments count
* Apply fixes from StyleCI (#1350)
2018-01-27 07:27:16 +08:00
|
|
|
static::saving(function (Post $post) {
|
|
|
|
$event = new GetModelIsPrivate($post);
|
|
|
|
|
|
|
|
$post->is_private = static::$dispatcher->until($event) === true;
|
|
|
|
});
|
|
|
|
|
2015-07-04 10:54:48 +08:00
|
|
|
static::deleted(function (Post $post) {
|
2017-06-24 19:43:33 +08:00
|
|
|
$post->raise(new Deleted($post));
|
2015-07-04 10:54:48 +08:00
|
|
|
});
|
|
|
|
|
|
|
|
static::addGlobalScope(new RegisteredTypesScope);
|
|
|
|
}
|
|
|
|
|
Overhaul model visibility scoping (#1342)
* Overhaul the way model visibility scoping works
- Previously post visibility scoping required concrete knowledge of the
parent discussion, ie. you needed a Discussion model on which you
would call `postsVisibleTo($actor)`. This meant that to fetch posts
from different discussions (eg. when listing user posts), it was a
convoluted process, ultimately causing #1333.
Now posts behave like any other model in terms of visibility scoping,
and you simply call `whereVisibleTo($actor)` on a Post query. This
scope will automatically apply a WHERE EXISTS clause that scopes the
query to only include posts whose discussions are visible too. Thus,
fetching posts from multiple discussions can now be done in a single
query, simplifying things greatly and fixing #1333.
- As such, the ScopePostVisibility event has been removed. Also, the
rest of the "Scope" events have been consolidated into a single event,
ScopeModelVisibility. This event is called whenever a user must have
a certain $ability in order to see a set of discussions. Typically
this ability is just "view". But in the case of discussions which have
been marked as `is_private`, it is "viewPrivate". And in the case of
discussions which have been hidden, it is "hide". etc.
The relevant API on AbstractPolicy has been refined, now providing
`find`, `findPrivate`, `findEmpty`, and `findWithPermission` methods.
This could probably do with further refinement and we can re-address
it once we get around to implementing more Extenders.
- An additional change is that Discussion::comments() (the relation
used to calculate the cached number of replies) now yields "comments
that are not private", where before it meant "comments that are
visible to Guests". This was flawed because eg. comments in non-public
tags are technically not visible to Guests.
Consequently, the Approval extension must adopt usage of `is_private`,
so that posts which are not approved are not included in the replies
count. Fundamentally, `is_private` now indicates that a discussion/
post should be hidden by default and should only be visible if it
meets certain criteria. This is in comparison to non-is_private
entities, which are visible by default and may be hidden if they don't
meet certain criteria.
Note that these changes have not been extensively tested, but I have
been over the logic multiple times and it seems to check out.
* Add event to determine whether a discussion `is_private`
See https://github.com/flarum/core/pull/1153#issuecomment-292693624
* Don't include hidden posts in the comments count
* Apply fixes from StyleCI (#1350)
2018-01-27 07:27:16 +08:00
|
|
|
/**
|
|
|
|
* @param Builder $query
|
|
|
|
* @param User $actor
|
|
|
|
*/
|
|
|
|
public function scopeWhereVisibleTo(Builder $query, User $actor)
|
|
|
|
{
|
|
|
|
static::$dispatcher->dispatch(
|
|
|
|
new ScopeModelVisibility($query, $actor, 'view')
|
|
|
|
);
|
|
|
|
|
|
|
|
// Make sure the post's discussion is visible as well
|
|
|
|
$query->whereExists(function ($query) use ($actor) {
|
|
|
|
$query->selectRaw('1')
|
|
|
|
->from('discussions')
|
|
|
|
->whereRaw('discussions.id = posts.discussion_id');
|
|
|
|
|
|
|
|
static::$dispatcher->dispatch(
|
|
|
|
new ScopeModelVisibility(Discussion::query()->setQuery($query), $actor, 'view')
|
|
|
|
);
|
|
|
|
});
|
|
|
|
}
|
|
|
|
|
2015-08-04 16:17:46 +08:00
|
|
|
/**
|
|
|
|
* Determine whether or not this post is visible to the given user.
|
|
|
|
*
|
|
|
|
* @param User $user
|
2016-02-26 11:09:39 +08:00
|
|
|
* @return bool
|
2015-08-04 16:17:46 +08:00
|
|
|
*/
|
|
|
|
public function isVisibleTo(User $user)
|
|
|
|
{
|
Overhaul model visibility scoping (#1342)
* Overhaul the way model visibility scoping works
- Previously post visibility scoping required concrete knowledge of the
parent discussion, ie. you needed a Discussion model on which you
would call `postsVisibleTo($actor)`. This meant that to fetch posts
from different discussions (eg. when listing user posts), it was a
convoluted process, ultimately causing #1333.
Now posts behave like any other model in terms of visibility scoping,
and you simply call `whereVisibleTo($actor)` on a Post query. This
scope will automatically apply a WHERE EXISTS clause that scopes the
query to only include posts whose discussions are visible too. Thus,
fetching posts from multiple discussions can now be done in a single
query, simplifying things greatly and fixing #1333.
- As such, the ScopePostVisibility event has been removed. Also, the
rest of the "Scope" events have been consolidated into a single event,
ScopeModelVisibility. This event is called whenever a user must have
a certain $ability in order to see a set of discussions. Typically
this ability is just "view". But in the case of discussions which have
been marked as `is_private`, it is "viewPrivate". And in the case of
discussions which have been hidden, it is "hide". etc.
The relevant API on AbstractPolicy has been refined, now providing
`find`, `findPrivate`, `findEmpty`, and `findWithPermission` methods.
This could probably do with further refinement and we can re-address
it once we get around to implementing more Extenders.
- An additional change is that Discussion::comments() (the relation
used to calculate the cached number of replies) now yields "comments
that are not private", where before it meant "comments that are
visible to Guests". This was flawed because eg. comments in non-public
tags are technically not visible to Guests.
Consequently, the Approval extension must adopt usage of `is_private`,
so that posts which are not approved are not included in the replies
count. Fundamentally, `is_private` now indicates that a discussion/
post should be hidden by default and should only be visible if it
meets certain criteria. This is in comparison to non-is_private
entities, which are visible by default and may be hidden if they don't
meet certain criteria.
Note that these changes have not been extensively tested, but I have
been over the logic multiple times and it seems to check out.
* Add event to determine whether a discussion `is_private`
See https://github.com/flarum/core/pull/1153#issuecomment-292693624
* Don't include hidden posts in the comments count
* Apply fixes from StyleCI (#1350)
2018-01-27 07:27:16 +08:00
|
|
|
return (bool) $this->newQuery()->whereVisibleTo($user)->find($this->id);
|
2015-08-04 16:17:46 +08:00
|
|
|
}
|
|
|
|
|
2015-07-04 10:54:48 +08:00
|
|
|
/**
|
|
|
|
* Define the relationship with the post's discussion.
|
|
|
|
*
|
|
|
|
* @return \Illuminate\Database\Eloquent\Relations\BelongsTo
|
|
|
|
*/
|
|
|
|
public function discussion()
|
|
|
|
{
|
2017-06-24 19:48:04 +08:00
|
|
|
return $this->belongsTo('Flarum\Discussion\Discussion', 'discussion_id');
|
2015-07-04 10:54:48 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Define the relationship with the post's author.
|
|
|
|
*
|
|
|
|
* @return \Illuminate\Database\Eloquent\Relations\BelongsTo
|
|
|
|
*/
|
|
|
|
public function user()
|
|
|
|
{
|
2017-06-24 18:55:22 +08:00
|
|
|
return $this->belongsTo('Flarum\User\User', 'user_id');
|
2015-07-04 10:54:48 +08:00
|
|
|
}
|
|
|
|
|
2015-07-06 14:56:27 +08:00
|
|
|
/**
|
|
|
|
* Define the relationship with the user who edited the post.
|
|
|
|
*
|
|
|
|
* @return \Illuminate\Database\Eloquent\Relations\BelongsTo
|
|
|
|
*/
|
|
|
|
public function editUser()
|
|
|
|
{
|
2017-06-24 18:55:22 +08:00
|
|
|
return $this->belongsTo('Flarum\User\User', 'edit_user_id');
|
2015-07-06 14:56:27 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Define the relationship with the user who hid the post.
|
|
|
|
*
|
|
|
|
* @return \Illuminate\Database\Eloquent\Relations\BelongsTo
|
|
|
|
*/
|
|
|
|
public function hideUser()
|
|
|
|
{
|
2017-06-24 18:55:22 +08:00
|
|
|
return $this->belongsTo('Flarum\User\User', 'hide_user_id');
|
2015-07-06 14:56:27 +08:00
|
|
|
}
|
|
|
|
|
2015-07-04 10:54:48 +08:00
|
|
|
/**
|
|
|
|
* Get all posts, regardless of their type, by removing the
|
|
|
|
* `RegisteredTypesScope` global scope constraints applied on this model.
|
|
|
|
*
|
|
|
|
* @param Builder $query
|
|
|
|
* @return Builder
|
|
|
|
*/
|
|
|
|
public function scopeAllTypes(Builder $query)
|
|
|
|
{
|
2018-01-21 05:58:08 +08:00
|
|
|
return $query->withoutGlobalScopes();
|
2015-07-04 10:54:48 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Create a new model instance according to the post's type.
|
|
|
|
*
|
|
|
|
* @param array $attributes
|
|
|
|
* @param string|null $connection
|
|
|
|
* @return static|object
|
|
|
|
*/
|
|
|
|
public function newFromBuilder($attributes = [], $connection = null)
|
|
|
|
{
|
|
|
|
$attributes = (array) $attributes;
|
|
|
|
|
|
|
|
if (! empty($attributes['type'])
|
|
|
|
&& isset(static::$models[$attributes['type']])
|
|
|
|
&& class_exists($class = static::$models[$attributes['type']])
|
|
|
|
) {
|
2015-07-18 21:29:47 +08:00
|
|
|
/** @var Post $instance */
|
2015-07-04 10:54:48 +08:00
|
|
|
$instance = new $class;
|
|
|
|
$instance->exists = true;
|
|
|
|
$instance->setRawAttributes($attributes, true);
|
|
|
|
$instance->setConnection($connection ?: $this->connection);
|
|
|
|
|
|
|
|
return $instance;
|
|
|
|
}
|
|
|
|
|
|
|
|
return parent::newFromBuilder($attributes, $connection);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Get the type-to-model map.
|
|
|
|
*
|
|
|
|
* @return array
|
|
|
|
*/
|
|
|
|
public static function getModels()
|
|
|
|
{
|
|
|
|
return static::$models;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Set the model for the given post type.
|
|
|
|
*
|
|
|
|
* @param string $type The post type.
|
|
|
|
* @param string $model The class name of the model for that type.
|
|
|
|
* @return void
|
|
|
|
*/
|
|
|
|
public static function setModel($type, $model)
|
|
|
|
{
|
|
|
|
static::$models[$type] = $model;
|
|
|
|
}
|
|
|
|
}
|