FIX: sort by column headings in topic list when filtered by tag
This commit is contained in:
parent
ffae39912f
commit
a5ca41b362
|
@ -132,7 +132,7 @@ export default function() {
|
|||
this.route('showCategory' + filter.capitalize(), {path: '/c/:category/:tag_id/l/' + filter});
|
||||
this.route('showParentCategory' + filter.capitalize(), {path: '/c/:parent_category/:category/:tag_id/l/' + filter});
|
||||
});
|
||||
this.route('show', {path: 'intersection/:tag_id/*additional_tags'});
|
||||
this.route('intersection', {path: 'intersection/:tag_id/*additional_tags'});
|
||||
});
|
||||
|
||||
this.route('tagGroups', {path: '/tag_groups', resetNamespace: true}, function() {
|
||||
|
|
|
@ -0,0 +1,9 @@
|
|||
import TagsShowRoute from 'discourse/routes/tags-show';
|
||||
|
||||
export default TagsShowRoute.extend({});
|
||||
|
||||
// The tags-intersection route is exactly the same as the tags-show route, but the wildcard at the
|
||||
// end of the route (*additional_tags) will cause a match when query parameters are present,
|
||||
// breaking all other tags-show routes. Ember thinks the query params are addition tags and should
|
||||
// be handled by the intersection logic. Defining tags-intersection as something separate avoids
|
||||
// that confusion.
|
Loading…
Reference in New Issue