我们在fluxible-router中有两条路线。我需要,如果访问legacyDek路由,那么在一个动作完成后,它将重定向到甲板路线。
deck: {
path: '/deck/:id(\\d+|\\d+-\\d+)/:stype?/:sid?/:spath?/:mode?/:theme?',
method: 'get',
page: 'deck',
handler: require('../components/Deck/Deck'),
action: (context, payload, done) => {
async.series([
(callback) => {
context.executeAction(loadDeck, payload, callback);
},
(callback) => {
context.executeAction(loadPresentation, payload, callback);
}
],
(err) => {
if(err) console.log(err);
done();
});
}
},
legacydeck: {
path: '/deck/:oldid(\\d+_\\w+.*)',
method: 'get',
action: (context, payload, done) => {
context.executeAction(loadLegacy, payload, (err, result) => {
if (err) console.log(err);
context.executeAction(navigateAction, {'url' : '/deck/' +result}, done);
});
}
},
重定向本身可以正常工作,但网址行保持不变。有人可以解释 - 为什么这个以及如何完全重定向?
答案 0 :(得分:0)
目前唯一的解决方案如下: 1.以这种方式更改触发重定向的操作,它返回一个错误对象,在我的示例中:
export default function loadLegacy(context, payload, done) {
log.info(context);
context.service.read('deck.legacy', {'oldid': parseInt(payload.params.oldid)}, {timeout: 20 * 1000}, (err, res) => {
// console.log('Executing loadPresentation action');
if (err) {
log.error(context, {filepath: __filename});
context.executeAction(serviceUnavailable, payload, done);
//context.dispatch('LOAD_FEATURED_FAILURE', err);
} else {
done({'statusCode':'301','redirectURL': '/deck/' + res.new_id});
}
});
}
context.getActionContext().executeAction(navigateAction, {url: req.url, reqId: req.reqId},
(err) => {
if (err) {
if (err.statusCode && err.statusCode === '301') { //handling redirect
res.redirect(err.redirectURL);
}else{ //handling other errors
...
}
}else{ //usual rendering
...
}
})
legacydeck: {
path: '/deck/:oldid(\\d+_\\w+.*)',
method: 'get',
action: (context, payload, done) => {
context.executeAction(loadLegacy, payload, done);
}
},