mirror of
https://github.com/flarum/core.git
synced 2025-10-11 23:14:29 +02:00
40a6d77e74
- Extract shared Ember components into a “flarum-common” ember-cli addon. This can be used by both the forum + admin Ember apps, keeping things DRY - Move LESS styles into their own top-level directory and do a similar thing (extract common styles) - Add LESS/JS compilation and versioning to PHP (AssetManager) - Set up admin entry point (Theoretical) upgrade instructions: - Delete everything in [app_root]/public - Set up tooling in forum/admin Ember apps (npm install/update, bower install/update) and then build them (ember build) - php artisan vendor:publish - Upgrade flarum/flarum repo (slight change in a config file) - If you need to trigger a LESS/JS recompile, delete the .css/.js files in [app_root]/public/flarum. I set up LiveReload to do this for me when I change files in less/ or ember/ Todo: - Start writing admin app! - Remove bootstrap/font-awesome from repo and instead depend on their composer packages? Maybe? (Bower is not an option here)
45 lines
1.5 KiB
JavaScript
45 lines
1.5 KiB
JavaScript
import Ember from 'ember';
|
|
|
|
import FadeIn from 'flarum-forum/mixins/fade-in';
|
|
import HasItemLists from 'flarum-forum/mixins/has-item-lists';
|
|
|
|
var precompileTemplate = Ember.Handlebars.compile;
|
|
|
|
/**
|
|
Component for a `discussionRenamed`-typed post.
|
|
*/
|
|
export default Ember.Component.extend(FadeIn, HasItemLists, {
|
|
layoutName: 'components/discussion/post-discussion-renamed',
|
|
tagName: 'article',
|
|
classNames: ['post', 'post-discussion-renamed', 'post-activity'],
|
|
itemLists: ['controls'],
|
|
|
|
// The stream-content component instansiates this component and sets the
|
|
// `content` property to the content of the item in the post-stream object.
|
|
// This happens to be our post model!
|
|
post: Ember.computed.alias('content'),
|
|
oldTitle: Ember.computed.alias('post.content.0'),
|
|
newTitle: Ember.computed.alias('post.content.1'),
|
|
|
|
populateControls: function(items) {
|
|
this.addActionItem(items, 'delete', 'Delete', 'times', 'post.canDelete');
|
|
},
|
|
|
|
actions: {
|
|
// In the template, we render the "controls" dropdown with the contents of
|
|
// the `renderControls` property. This way, when a post is initially
|
|
// rendered, it doesn't have to go to the trouble of rendering the
|
|
// controls right away, which speeds things up. When the dropdown button
|
|
// is clicked, this will fill in the actual controls.
|
|
renderControls: function() {
|
|
this.set('renderControls', this.get('controls'));
|
|
},
|
|
|
|
delete: function() {
|
|
var post = this.get('post');
|
|
post.destroyRecord();
|
|
this.sendAction('postRemoved', post);
|
|
}
|
|
}
|
|
});
|