✨Dynamic Routing Beta (#9596)
refs #9601
### Dynamic Routing
This is the beta version of dynamic routing.
- we had a initial implementation of "channels" available in the codebase
- we have removed and moved this implementation
- there is now a centralised place for dynamic routing - server/services/routing
- each routing component is represented by a router type e.g. collections, routes, static pages, taxonomies, rss, preview of posts
- keep as much as possible logic of routing helpers, middlewares and controllers
- ensure test coverage
- connect all the things together
- yaml file + validation
- routing + routers
- url service
- sitemaps
- url access
- deeper implementation of yaml validations
- e.g. hard require slashes
- ensure routing hierarchy/order
- e.g. you enable the subscriber app
- you have a custom static page, which lives under the same slug /subscribe
- static pages are stronger than apps
- e.g. the first collection owns the post it has filtered
- a post cannot live in two collections
- ensure apps are still working and hook into the routers layer (or better said: and register in the routing service)
- put as much as possible comments to the code base for better understanding
- ensure a clean debug log
- ensure we can unmount routes
- e.g. you have a collection permalink of /:slug/ represented by {globals.permalink}
- and you change the permalink in the admin to dated permalink
- the express route get's refreshed from /:slug/ to /:year/:month/:day/:slug/
- unmount without server restart, yey
- ensure we are backwards compatible
- e.g. render home.hbs for collection index if collection route is /
- ensure you can access your configured permalink from the settings table with {globals.permalink}
### Render 503 if url service did not finish
- return 503 if the url service has not finished generating the resource urls
### Rewrite sitemaps
- we have rewritten the sitemaps "service", because the url generator does no longer happen on runtime
- we generate all urls on bootstrap
- the sitemaps service will consume created resource and router urls
- these urls will be shown on the xml pages
- we listen on url events
- we listen on router events
- we no longer have to fetch the resources, which is nice
- the urlservice pre-fetches resources and emits their urls
- the urlservice is the only component who knows which urls are valid
- i made some ES6 adaptions
- we keep the caching logic -> only regenerate xml if there is a change
- updated tests
- checked test coverage (100%)
### Re-work usage of Url utility
- replace all usages of `urlService.utils.urlFor` by `urlService.getByResourceId`
- only for resources e.g. post, author, tag
- this is important, because with dynamic routing we no longer create static urls based on the settings permalink on runtime
- adapt url utility
- adapt tests
2018-06-05 20:02:20 +03:00
|
|
|
const should = require('should'),
|
|
|
|
sinon = require('sinon'),
|
|
|
|
Promise = require('bluebird'),
|
|
|
|
testUtils = require('../../../../utils'),
|
|
|
|
configUtils = require('../../../../utils/configUtils'),
|
2020-03-30 18:26:47 +03:00
|
|
|
api = require('../../../../../core/server/api'),
|
|
|
|
controllers = require('../../../../../core/frontend/services/routing/controllers'),
|
|
|
|
helpers = require('../../../../../core/frontend/services/routing/helpers'),
|
|
|
|
urlService = require('../../../../../core/frontend/services/url'),
|
|
|
|
urlUtils = require('../../../../../core/server/lib/url-utils'),
|
2019-06-18 16:13:55 +03:00
|
|
|
|
2019-03-11 17:04:52 +03:00
|
|
|
EDITOR_URL = '/editor/post/';
|
✨Dynamic Routing Beta (#9596)
refs #9601
### Dynamic Routing
This is the beta version of dynamic routing.
- we had a initial implementation of "channels" available in the codebase
- we have removed and moved this implementation
- there is now a centralised place for dynamic routing - server/services/routing
- each routing component is represented by a router type e.g. collections, routes, static pages, taxonomies, rss, preview of posts
- keep as much as possible logic of routing helpers, middlewares and controllers
- ensure test coverage
- connect all the things together
- yaml file + validation
- routing + routers
- url service
- sitemaps
- url access
- deeper implementation of yaml validations
- e.g. hard require slashes
- ensure routing hierarchy/order
- e.g. you enable the subscriber app
- you have a custom static page, which lives under the same slug /subscribe
- static pages are stronger than apps
- e.g. the first collection owns the post it has filtered
- a post cannot live in two collections
- ensure apps are still working and hook into the routers layer (or better said: and register in the routing service)
- put as much as possible comments to the code base for better understanding
- ensure a clean debug log
- ensure we can unmount routes
- e.g. you have a collection permalink of /:slug/ represented by {globals.permalink}
- and you change the permalink in the admin to dated permalink
- the express route get's refreshed from /:slug/ to /:year/:month/:day/:slug/
- unmount without server restart, yey
- ensure we are backwards compatible
- e.g. render home.hbs for collection index if collection route is /
- ensure you can access your configured permalink from the settings table with {globals.permalink}
### Render 503 if url service did not finish
- return 503 if the url service has not finished generating the resource urls
### Rewrite sitemaps
- we have rewritten the sitemaps "service", because the url generator does no longer happen on runtime
- we generate all urls on bootstrap
- the sitemaps service will consume created resource and router urls
- these urls will be shown on the xml pages
- we listen on url events
- we listen on router events
- we no longer have to fetch the resources, which is nice
- the urlservice pre-fetches resources and emits their urls
- the urlservice is the only component who knows which urls are valid
- i made some ES6 adaptions
- we keep the caching logic -> only regenerate xml if there is a change
- updated tests
- checked test coverage (100%)
### Re-work usage of Url utility
- replace all usages of `urlService.utils.urlFor` by `urlService.getByResourceId`
- only for resources e.g. post, author, tag
- this is important, because with dynamic routing we no longer create static urls based on the settings permalink on runtime
- adapt url utility
- adapt tests
2018-06-05 20:02:20 +03:00
|
|
|
|
|
|
|
describe('Unit - services/routing/controllers/preview', function () {
|
|
|
|
let secureStub, renderStub;
|
|
|
|
let req, res, post, apiResponse;
|
|
|
|
|
|
|
|
function failTest(done) {
|
|
|
|
return function (err) {
|
|
|
|
should.exist(err);
|
|
|
|
done(err);
|
|
|
|
};
|
|
|
|
}
|
|
|
|
|
|
|
|
afterEach(function () {
|
2019-01-21 19:53:44 +03:00
|
|
|
sinon.restore();
|
✨Dynamic Routing Beta (#9596)
refs #9601
### Dynamic Routing
This is the beta version of dynamic routing.
- we had a initial implementation of "channels" available in the codebase
- we have removed and moved this implementation
- there is now a centralised place for dynamic routing - server/services/routing
- each routing component is represented by a router type e.g. collections, routes, static pages, taxonomies, rss, preview of posts
- keep as much as possible logic of routing helpers, middlewares and controllers
- ensure test coverage
- connect all the things together
- yaml file + validation
- routing + routers
- url service
- sitemaps
- url access
- deeper implementation of yaml validations
- e.g. hard require slashes
- ensure routing hierarchy/order
- e.g. you enable the subscriber app
- you have a custom static page, which lives under the same slug /subscribe
- static pages are stronger than apps
- e.g. the first collection owns the post it has filtered
- a post cannot live in two collections
- ensure apps are still working and hook into the routers layer (or better said: and register in the routing service)
- put as much as possible comments to the code base for better understanding
- ensure a clean debug log
- ensure we can unmount routes
- e.g. you have a collection permalink of /:slug/ represented by {globals.permalink}
- and you change the permalink in the admin to dated permalink
- the express route get's refreshed from /:slug/ to /:year/:month/:day/:slug/
- unmount without server restart, yey
- ensure we are backwards compatible
- e.g. render home.hbs for collection index if collection route is /
- ensure you can access your configured permalink from the settings table with {globals.permalink}
### Render 503 if url service did not finish
- return 503 if the url service has not finished generating the resource urls
### Rewrite sitemaps
- we have rewritten the sitemaps "service", because the url generator does no longer happen on runtime
- we generate all urls on bootstrap
- the sitemaps service will consume created resource and router urls
- these urls will be shown on the xml pages
- we listen on url events
- we listen on router events
- we no longer have to fetch the resources, which is nice
- the urlservice pre-fetches resources and emits their urls
- the urlservice is the only component who knows which urls are valid
- i made some ES6 adaptions
- we keep the caching logic -> only regenerate xml if there is a change
- updated tests
- checked test coverage (100%)
### Re-work usage of Url utility
- replace all usages of `urlService.utils.urlFor` by `urlService.getByResourceId`
- only for resources e.g. post, author, tag
- this is important, because with dynamic routing we no longer create static urls based on the settings permalink on runtime
- adapt url utility
- adapt tests
2018-06-05 20:02:20 +03:00
|
|
|
configUtils.restore();
|
|
|
|
});
|
|
|
|
|
2018-10-17 19:15:43 +03:00
|
|
|
describe('v2', function () {
|
|
|
|
let previewStub;
|
|
|
|
|
|
|
|
beforeEach(function () {
|
|
|
|
post = testUtils.DataGenerator.forKnex.createPost({status: 'draft'});
|
|
|
|
|
|
|
|
apiResponse = {
|
|
|
|
preview: [post]
|
|
|
|
};
|
|
|
|
|
|
|
|
req = {
|
|
|
|
path: '/',
|
|
|
|
params: {
|
|
|
|
uuid: 'something'
|
|
|
|
},
|
|
|
|
route: {}
|
|
|
|
};
|
|
|
|
|
|
|
|
res = {
|
|
|
|
routerOptions: {
|
2019-01-04 23:59:39 +03:00
|
|
|
query: {controller: 'preview', resource: 'preview'}
|
2018-10-17 19:15:43 +03:00
|
|
|
},
|
|
|
|
locals: {
|
|
|
|
apiVersion: 'v2'
|
|
|
|
},
|
|
|
|
render: sinon.spy(),
|
|
|
|
redirect: sinon.spy(),
|
|
|
|
set: sinon.spy()
|
|
|
|
};
|
|
|
|
|
2019-01-21 19:53:44 +03:00
|
|
|
secureStub = sinon.stub();
|
2018-10-17 19:15:43 +03:00
|
|
|
|
2019-06-18 16:13:55 +03:00
|
|
|
sinon.stub(urlUtils, 'redirectToAdmin');
|
|
|
|
sinon.stub(urlUtils, 'redirect301');
|
2019-01-21 19:53:44 +03:00
|
|
|
sinon.stub(urlService, 'getUrlByResourceId');
|
2018-10-17 19:15:43 +03:00
|
|
|
|
2019-01-21 19:53:44 +03:00
|
|
|
sinon.stub(helpers, 'secure').get(function () {
|
2018-10-17 19:15:43 +03:00
|
|
|
return secureStub;
|
|
|
|
});
|
|
|
|
|
2019-04-15 17:15:32 +03:00
|
|
|
renderStub = sinon.stub();
|
2019-01-21 19:53:44 +03:00
|
|
|
sinon.stub(helpers, 'renderEntry').get(function () {
|
2019-04-15 17:15:32 +03:00
|
|
|
return function () {
|
|
|
|
return renderStub;
|
|
|
|
};
|
2018-10-17 19:15:43 +03:00
|
|
|
});
|
|
|
|
|
2019-01-21 19:53:44 +03:00
|
|
|
previewStub = sinon.stub();
|
2018-10-17 19:15:43 +03:00
|
|
|
previewStub.withArgs({
|
|
|
|
uuid: req.params.uuid,
|
|
|
|
status: 'all',
|
2019-09-10 12:41:42 +03:00
|
|
|
include: 'authors,tags'
|
2018-10-17 19:15:43 +03:00
|
|
|
}).resolves(apiResponse);
|
|
|
|
|
2019-01-21 19:53:44 +03:00
|
|
|
sinon.stub(api.v2, 'preview').get(() => {
|
2018-10-17 19:15:43 +03:00
|
|
|
return {
|
|
|
|
read: previewStub
|
|
|
|
};
|
|
|
|
});
|
✨Dynamic Routing Beta (#9596)
refs #9601
### Dynamic Routing
This is the beta version of dynamic routing.
- we had a initial implementation of "channels" available in the codebase
- we have removed and moved this implementation
- there is now a centralised place for dynamic routing - server/services/routing
- each routing component is represented by a router type e.g. collections, routes, static pages, taxonomies, rss, preview of posts
- keep as much as possible logic of routing helpers, middlewares and controllers
- ensure test coverage
- connect all the things together
- yaml file + validation
- routing + routers
- url service
- sitemaps
- url access
- deeper implementation of yaml validations
- e.g. hard require slashes
- ensure routing hierarchy/order
- e.g. you enable the subscriber app
- you have a custom static page, which lives under the same slug /subscribe
- static pages are stronger than apps
- e.g. the first collection owns the post it has filtered
- a post cannot live in two collections
- ensure apps are still working and hook into the routers layer (or better said: and register in the routing service)
- put as much as possible comments to the code base for better understanding
- ensure a clean debug log
- ensure we can unmount routes
- e.g. you have a collection permalink of /:slug/ represented by {globals.permalink}
- and you change the permalink in the admin to dated permalink
- the express route get's refreshed from /:slug/ to /:year/:month/:day/:slug/
- unmount without server restart, yey
- ensure we are backwards compatible
- e.g. render home.hbs for collection index if collection route is /
- ensure you can access your configured permalink from the settings table with {globals.permalink}
### Render 503 if url service did not finish
- return 503 if the url service has not finished generating the resource urls
### Rewrite sitemaps
- we have rewritten the sitemaps "service", because the url generator does no longer happen on runtime
- we generate all urls on bootstrap
- the sitemaps service will consume created resource and router urls
- these urls will be shown on the xml pages
- we listen on url events
- we listen on router events
- we no longer have to fetch the resources, which is nice
- the urlservice pre-fetches resources and emits their urls
- the urlservice is the only component who knows which urls are valid
- i made some ES6 adaptions
- we keep the caching logic -> only regenerate xml if there is a change
- updated tests
- checked test coverage (100%)
### Re-work usage of Url utility
- replace all usages of `urlService.utils.urlFor` by `urlService.getByResourceId`
- only for resources e.g. post, author, tag
- this is important, because with dynamic routing we no longer create static urls based on the settings permalink on runtime
- adapt url utility
- adapt tests
2018-06-05 20:02:20 +03:00
|
|
|
});
|
|
|
|
|
2018-10-17 19:15:43 +03:00
|
|
|
it('should render post', function (done) {
|
2019-04-15 17:15:32 +03:00
|
|
|
controllers.preview(req, res, failTest(done)).then(function () {
|
2018-10-17 19:15:43 +03:00
|
|
|
renderStub.called.should.be.true();
|
|
|
|
secureStub.called.should.be.true();
|
|
|
|
done();
|
2019-04-15 17:15:32 +03:00
|
|
|
}).catch(done);
|
✨Dynamic Routing Beta (#9596)
refs #9601
### Dynamic Routing
This is the beta version of dynamic routing.
- we had a initial implementation of "channels" available in the codebase
- we have removed and moved this implementation
- there is now a centralised place for dynamic routing - server/services/routing
- each routing component is represented by a router type e.g. collections, routes, static pages, taxonomies, rss, preview of posts
- keep as much as possible logic of routing helpers, middlewares and controllers
- ensure test coverage
- connect all the things together
- yaml file + validation
- routing + routers
- url service
- sitemaps
- url access
- deeper implementation of yaml validations
- e.g. hard require slashes
- ensure routing hierarchy/order
- e.g. you enable the subscriber app
- you have a custom static page, which lives under the same slug /subscribe
- static pages are stronger than apps
- e.g. the first collection owns the post it has filtered
- a post cannot live in two collections
- ensure apps are still working and hook into the routers layer (or better said: and register in the routing service)
- put as much as possible comments to the code base for better understanding
- ensure a clean debug log
- ensure we can unmount routes
- e.g. you have a collection permalink of /:slug/ represented by {globals.permalink}
- and you change the permalink in the admin to dated permalink
- the express route get's refreshed from /:slug/ to /:year/:month/:day/:slug/
- unmount without server restart, yey
- ensure we are backwards compatible
- e.g. render home.hbs for collection index if collection route is /
- ensure you can access your configured permalink from the settings table with {globals.permalink}
### Render 503 if url service did not finish
- return 503 if the url service has not finished generating the resource urls
### Rewrite sitemaps
- we have rewritten the sitemaps "service", because the url generator does no longer happen on runtime
- we generate all urls on bootstrap
- the sitemaps service will consume created resource and router urls
- these urls will be shown on the xml pages
- we listen on url events
- we listen on router events
- we no longer have to fetch the resources, which is nice
- the urlservice pre-fetches resources and emits their urls
- the urlservice is the only component who knows which urls are valid
- i made some ES6 adaptions
- we keep the caching logic -> only regenerate xml if there is a change
- updated tests
- checked test coverage (100%)
### Re-work usage of Url utility
- replace all usages of `urlService.utils.urlFor` by `urlService.getByResourceId`
- only for resources e.g. post, author, tag
- this is important, because with dynamic routing we no longer create static urls based on the settings permalink on runtime
- adapt url utility
- adapt tests
2018-06-05 20:02:20 +03:00
|
|
|
});
|
|
|
|
});
|
2019-08-09 17:25:12 +03:00
|
|
|
|
|
|
|
describe('canary', function () {
|
|
|
|
let previewStub;
|
|
|
|
|
|
|
|
beforeEach(function () {
|
|
|
|
post = testUtils.DataGenerator.forKnex.createPost({status: 'draft'});
|
|
|
|
|
|
|
|
apiResponse = {
|
|
|
|
preview: [post]
|
|
|
|
};
|
|
|
|
|
|
|
|
req = {
|
|
|
|
path: '/',
|
|
|
|
params: {
|
|
|
|
uuid: 'something'
|
|
|
|
},
|
|
|
|
route: {}
|
|
|
|
};
|
|
|
|
|
|
|
|
res = {
|
|
|
|
routerOptions: {
|
|
|
|
query: {controller: 'preview', resource: 'preview'}
|
|
|
|
},
|
|
|
|
locals: {
|
|
|
|
apiVersion: 'canary'
|
|
|
|
},
|
|
|
|
render: sinon.spy(),
|
|
|
|
redirect: sinon.spy(),
|
|
|
|
set: sinon.spy()
|
|
|
|
};
|
|
|
|
|
|
|
|
secureStub = sinon.stub();
|
|
|
|
|
|
|
|
sinon.stub(urlUtils, 'redirectToAdmin');
|
|
|
|
sinon.stub(urlUtils, 'redirect301');
|
|
|
|
sinon.stub(urlService, 'getUrlByResourceId');
|
|
|
|
|
|
|
|
sinon.stub(helpers, 'secure').get(function () {
|
|
|
|
return secureStub;
|
|
|
|
});
|
|
|
|
|
|
|
|
renderStub = sinon.stub();
|
|
|
|
sinon.stub(helpers, 'renderEntry').get(function () {
|
|
|
|
return function () {
|
|
|
|
return renderStub;
|
|
|
|
};
|
|
|
|
});
|
|
|
|
|
|
|
|
previewStub = sinon.stub();
|
|
|
|
previewStub.withArgs({
|
|
|
|
uuid: req.params.uuid,
|
|
|
|
status: 'all',
|
2019-09-10 12:41:42 +03:00
|
|
|
include: 'authors,tags'
|
2019-08-09 17:25:12 +03:00
|
|
|
}).resolves(apiResponse);
|
|
|
|
|
|
|
|
sinon.stub(api.canary, 'preview').get(() => {
|
|
|
|
return {
|
|
|
|
read: previewStub
|
|
|
|
};
|
|
|
|
});
|
|
|
|
});
|
|
|
|
|
|
|
|
it('should render post', function (done) {
|
|
|
|
controllers.preview(req, res, failTest(done)).then(function () {
|
|
|
|
renderStub.called.should.be.true();
|
|
|
|
secureStub.called.should.be.true();
|
|
|
|
done();
|
|
|
|
}).catch(done);
|
|
|
|
});
|
|
|
|
});
|
2019-09-03 10:03:31 +03:00
|
|
|
|
|
|
|
describe('v3', function () {
|
|
|
|
let previewStub;
|
|
|
|
|
|
|
|
beforeEach(function () {
|
|
|
|
post = testUtils.DataGenerator.forKnex.createPost({status: 'draft'});
|
|
|
|
|
|
|
|
apiResponse = {
|
|
|
|
preview: [post]
|
|
|
|
};
|
|
|
|
|
|
|
|
req = {
|
|
|
|
path: '/',
|
|
|
|
params: {
|
|
|
|
uuid: 'something'
|
|
|
|
},
|
|
|
|
route: {}
|
|
|
|
};
|
|
|
|
|
|
|
|
res = {
|
|
|
|
routerOptions: {
|
|
|
|
query: {controller: 'preview', resource: 'preview'}
|
|
|
|
},
|
|
|
|
locals: {
|
|
|
|
apiVersion: 'v3'
|
|
|
|
},
|
|
|
|
render: sinon.spy(),
|
|
|
|
redirect: sinon.spy(),
|
|
|
|
set: sinon.spy()
|
|
|
|
};
|
|
|
|
|
|
|
|
secureStub = sinon.stub();
|
|
|
|
|
|
|
|
sinon.stub(urlUtils, 'redirectToAdmin');
|
|
|
|
sinon.stub(urlUtils, 'redirect301');
|
|
|
|
sinon.stub(urlService, 'getUrlByResourceId');
|
|
|
|
|
|
|
|
sinon.stub(helpers, 'secure').get(function () {
|
|
|
|
return secureStub;
|
|
|
|
});
|
|
|
|
|
|
|
|
renderStub = sinon.stub();
|
|
|
|
sinon.stub(helpers, 'renderEntry').get(function () {
|
|
|
|
return function () {
|
|
|
|
return renderStub;
|
|
|
|
};
|
|
|
|
});
|
|
|
|
|
|
|
|
previewStub = sinon.stub();
|
|
|
|
previewStub.withArgs({
|
|
|
|
uuid: req.params.uuid,
|
|
|
|
status: 'all',
|
2019-09-10 12:41:42 +03:00
|
|
|
include: 'authors,tags'
|
2019-09-03 10:03:31 +03:00
|
|
|
}).resolves(apiResponse);
|
|
|
|
|
|
|
|
sinon.stub(api.v3, 'preview').get(() => {
|
|
|
|
return {
|
|
|
|
read: previewStub
|
|
|
|
};
|
|
|
|
});
|
|
|
|
});
|
|
|
|
|
|
|
|
it('should render post', function (done) {
|
|
|
|
controllers.preview(req, res, failTest(done)).then(function () {
|
|
|
|
renderStub.called.should.be.true();
|
|
|
|
secureStub.called.should.be.true();
|
|
|
|
done();
|
|
|
|
}).catch(done);
|
|
|
|
});
|
|
|
|
});
|
✨Dynamic Routing Beta (#9596)
refs #9601
### Dynamic Routing
This is the beta version of dynamic routing.
- we had a initial implementation of "channels" available in the codebase
- we have removed and moved this implementation
- there is now a centralised place for dynamic routing - server/services/routing
- each routing component is represented by a router type e.g. collections, routes, static pages, taxonomies, rss, preview of posts
- keep as much as possible logic of routing helpers, middlewares and controllers
- ensure test coverage
- connect all the things together
- yaml file + validation
- routing + routers
- url service
- sitemaps
- url access
- deeper implementation of yaml validations
- e.g. hard require slashes
- ensure routing hierarchy/order
- e.g. you enable the subscriber app
- you have a custom static page, which lives under the same slug /subscribe
- static pages are stronger than apps
- e.g. the first collection owns the post it has filtered
- a post cannot live in two collections
- ensure apps are still working and hook into the routers layer (or better said: and register in the routing service)
- put as much as possible comments to the code base for better understanding
- ensure a clean debug log
- ensure we can unmount routes
- e.g. you have a collection permalink of /:slug/ represented by {globals.permalink}
- and you change the permalink in the admin to dated permalink
- the express route get's refreshed from /:slug/ to /:year/:month/:day/:slug/
- unmount without server restart, yey
- ensure we are backwards compatible
- e.g. render home.hbs for collection index if collection route is /
- ensure you can access your configured permalink from the settings table with {globals.permalink}
### Render 503 if url service did not finish
- return 503 if the url service has not finished generating the resource urls
### Rewrite sitemaps
- we have rewritten the sitemaps "service", because the url generator does no longer happen on runtime
- we generate all urls on bootstrap
- the sitemaps service will consume created resource and router urls
- these urls will be shown on the xml pages
- we listen on url events
- we listen on router events
- we no longer have to fetch the resources, which is nice
- the urlservice pre-fetches resources and emits their urls
- the urlservice is the only component who knows which urls are valid
- i made some ES6 adaptions
- we keep the caching logic -> only regenerate xml if there is a change
- updated tests
- checked test coverage (100%)
### Re-work usage of Url utility
- replace all usages of `urlService.utils.urlFor` by `urlService.getByResourceId`
- only for resources e.g. post, author, tag
- this is important, because with dynamic routing we no longer create static urls based on the settings permalink on runtime
- adapt url utility
- adapt tests
2018-06-05 20:02:20 +03:00
|
|
|
});
|