2018-06-02 22:48:23 +03:00
|
|
|
var should = require('should'),
|
2017-03-21 11:24:11 +03:00
|
|
|
sinon = require('sinon'),
|
|
|
|
Promise = require('bluebird'),
|
✨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
|
|
|
testUtils = require('../../utils'),
|
2017-03-21 11:24:11 +03:00
|
|
|
configUtils = require('../../utils/configUtils'),
|
2017-05-31 17:46:29 +03:00
|
|
|
markdownToMobiledoc = require('../../utils/fixtures/data-generator').markdownToMobiledoc,
|
2017-03-21 11:24:11 +03:00
|
|
|
helpers = require('../../../server/helpers'),
|
✨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
|
|
|
urlService = require('../../../server/services/url'),
|
2019-01-21 19:53:44 +03:00
|
|
|
api = require('../../../server/api');
|
2014-10-10 18:54:07 +04:00
|
|
|
|
|
|
|
describe('{{url}} helper', function () {
|
2017-03-21 11:24:11 +03:00
|
|
|
var rendered;
|
2014-10-10 18:54:07 +04:00
|
|
|
|
|
|
|
before(function () {
|
2017-04-03 18:29:36 +03:00
|
|
|
configUtils.set({url: 'http://localhost:82832/'});
|
2014-10-10 18:54:07 +04:00
|
|
|
});
|
|
|
|
|
|
|
|
beforeEach(function () {
|
2015-09-26 00:31:54 +03:00
|
|
|
rendered = null;
|
✨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-01-21 19:53:44 +03:00
|
|
|
sinon.stub(urlService, 'getUrlByResourceId');
|
✨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-01-21 19:53:44 +03:00
|
|
|
sinon.stub(api.settings, 'read').callsFake(function () {
|
2014-10-10 18:54:07 +04:00
|
|
|
return Promise.resolve({settings: [{value: '/:slug/'}]});
|
|
|
|
});
|
|
|
|
});
|
|
|
|
|
|
|
|
afterEach(function () {
|
2019-01-21 19:53:44 +03:00
|
|
|
sinon.restore();
|
2014-10-10 18:54:07 +04:00
|
|
|
});
|
|
|
|
|
|
|
|
after(function () {
|
2015-12-14 23:05:11 +03:00
|
|
|
configUtils.restore();
|
2014-10-10 18:54:07 +04:00
|
|
|
});
|
|
|
|
|
2014-12-28 22:38:29 +03:00
|
|
|
it('should return the slug with a prefix slash if the context is a post', function () {
|
✨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 post = testUtils.DataGenerator.forKnex.createPost({
|
2014-10-10 18:54:07 +04:00
|
|
|
html: 'content',
|
2017-05-31 17:46:29 +03:00
|
|
|
mobiledoc: markdownToMobiledoc('ff'),
|
2014-10-10 18:54:07 +04:00
|
|
|
title: 'title',
|
|
|
|
slug: 'slug',
|
2014-12-10 17:03:39 +03:00
|
|
|
created_at: new Date(0),
|
|
|
|
url: '/slug/'
|
2014-12-28 22:38:29 +03:00
|
|
|
});
|
|
|
|
|
2018-06-12 18:36:58 +03:00
|
|
|
urlService.getUrlByResourceId.withArgs(post.id, {absolute: undefined, secure: undefined, withSubdirectory: true}).returns('/slug/');
|
✨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
|
|
|
|
|
|
|
rendered = helpers.url.call(post);
|
2014-12-28 22:38:29 +03:00
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('/slug/');
|
2014-10-10 18:54:07 +04:00
|
|
|
});
|
|
|
|
|
2014-12-28 22:38:29 +03:00
|
|
|
it('should output an absolute URL if the option is present', function () {
|
✨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 post = testUtils.DataGenerator.forKnex.createPost({
|
|
|
|
html: 'content',
|
|
|
|
mobiledoc: markdownToMobiledoc('ff'),
|
|
|
|
title: 'title',
|
|
|
|
slug: 'slug',
|
|
|
|
url: '/slug/',
|
|
|
|
created_at: new Date(0)
|
|
|
|
});
|
|
|
|
|
2019-03-04 13:23:42 +03:00
|
|
|
urlService.getUrlByResourceId.withArgs(post.id, {absolute: true, secure: undefined, withSubdirectory: true}).returns('http://localhost:82832/slug/');
|
2014-12-28 22:38:29 +03:00
|
|
|
|
✨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
|
|
|
rendered = helpers.url.call(post, {hash: {absolute: 'true'}});
|
2014-12-28 22:38:29 +03:00
|
|
|
should.exist(rendered);
|
2017-04-03 18:29:36 +03:00
|
|
|
rendered.string.should.equal('http://localhost:82832/slug/');
|
2014-10-10 18:54:07 +04:00
|
|
|
});
|
|
|
|
|
2016-01-05 21:04:39 +03:00
|
|
|
it('should output an absolute URL with https if the option is present and secure', function () {
|
✨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 post = testUtils.DataGenerator.forKnex.createPost({
|
|
|
|
html: 'content',
|
|
|
|
mobiledoc: markdownToMobiledoc('ff'),
|
|
|
|
title: 'title',
|
|
|
|
slug: 'slug',
|
|
|
|
url: '/slug/',
|
|
|
|
created_at: new Date(0),
|
|
|
|
secure: true
|
|
|
|
});
|
2016-01-05 21:04:39 +03:00
|
|
|
|
2019-03-04 13:23:42 +03:00
|
|
|
urlService.getUrlByResourceId.withArgs(post.id, {absolute: true, secure: true, withSubdirectory: true}).returns('https://localhost:82832/slug/');
|
2016-01-05 21:04:39 +03:00
|
|
|
|
✨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
|
|
|
rendered = helpers.url.call(post, {hash: {absolute: 'true'}});
|
2016-01-05 21:04:39 +03:00
|
|
|
should.exist(rendered);
|
2017-04-03 18:29:36 +03:00
|
|
|
rendered.string.should.equal('https://localhost:82832/slug/');
|
2016-01-05 21:04:39 +03:00
|
|
|
});
|
|
|
|
|
2014-12-28 22:38:29 +03:00
|
|
|
it('should return the slug with a prefixed /tag/ if the context is a tag', function () {
|
✨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 tag = testUtils.DataGenerator.forKnex.createTag({
|
2014-10-10 18:54:07 +04:00
|
|
|
name: 'the tag',
|
|
|
|
slug: 'the-tag',
|
|
|
|
description: null,
|
|
|
|
parent: null
|
2014-12-28 22:38:29 +03:00
|
|
|
});
|
|
|
|
|
2018-06-12 18:36:58 +03:00
|
|
|
urlService.getUrlByResourceId.withArgs(tag.id, {absolute: undefined, secure: undefined, withSubdirectory: true}).returns('/tag/the-tag/');
|
✨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
|
|
|
|
|
|
|
rendered = helpers.url.call(tag);
|
2014-12-28 22:38:29 +03:00
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('/tag/the-tag/');
|
2014-10-10 18:54:07 +04:00
|
|
|
});
|
|
|
|
|
2017-10-05 14:50:55 +03:00
|
|
|
it('should return the slug with a prefixed /author/ if the context is author', function () {
|
✨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 user = testUtils.DataGenerator.forKnex.createUser({
|
2017-10-05 14:50:55 +03:00
|
|
|
bio: null,
|
|
|
|
website: null,
|
|
|
|
profile_image: null,
|
|
|
|
location: null,
|
|
|
|
slug: 'some-author'
|
|
|
|
});
|
|
|
|
|
2018-06-12 18:36:58 +03:00
|
|
|
urlService.getUrlByResourceId.withArgs(user.id, {absolute: undefined, secure: undefined, withSubdirectory: true}).returns('/author/some-author/');
|
✨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
|
|
|
|
|
|
|
rendered = helpers.url.call(user);
|
2017-10-05 14:50:55 +03:00
|
|
|
should.exist(rendered);
|
|
|
|
rendered.string.should.equal('/author/some-author/');
|
|
|
|
});
|
|
|
|
|
2014-12-28 22:38:29 +03:00
|
|
|
it('should return / if not a post or tag', function () {
|
✨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
|
|
|
rendered = helpers.url.call({something: 'key'});
|
2014-12-28 22:38:29 +03:00
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('/');
|
2014-10-10 18:54:07 +04:00
|
|
|
});
|
2015-01-28 08:57:19 +03:00
|
|
|
|
|
|
|
it('should return a relative url if passed through a nav context', function () {
|
2015-09-26 00:31:54 +03:00
|
|
|
rendered = helpers.url.call(
|
2015-01-28 08:57:19 +03:00
|
|
|
{url: '/foo', label: 'Foo', slug: 'foo', current: true});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('/foo');
|
2015-01-28 08:57:19 +03:00
|
|
|
});
|
|
|
|
|
|
|
|
it('should return an absolute url if passed through a nav context', function () {
|
2015-09-26 00:31:54 +03:00
|
|
|
rendered = helpers.url.call(
|
2015-01-28 08:57:19 +03:00
|
|
|
{url: '/bar', label: 'Bar', slug: 'bar', current: true},
|
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-04-03 18:29:36 +03:00
|
|
|
rendered.string.should.equal('http://localhost:82832/bar');
|
2015-01-28 08:57:19 +03:00
|
|
|
});
|
|
|
|
|
2016-01-05 21:04:39 +03:00
|
|
|
it('should return an absolute url with https if context is secure', function () {
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: '/bar', label: 'Bar', slug: 'bar', current: true, secure: true},
|
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-04-03 18:29:36 +03:00
|
|
|
rendered.string.should.equal('https://localhost:82832/bar');
|
2016-01-05 21:04:39 +03:00
|
|
|
});
|
|
|
|
|
2015-01-28 08:57:19 +03:00
|
|
|
it('external urls should be retained in a nav context', function () {
|
2015-09-26 00:31:54 +03:00
|
|
|
rendered = helpers.url.call(
|
2015-01-28 08:57:19 +03:00
|
|
|
{url: 'http://casper.website/baz', label: 'Baz', slug: 'baz', current: true},
|
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('http://casper.website/baz');
|
2015-01-28 08:57:19 +03:00
|
|
|
});
|
|
|
|
|
|
|
|
it('should handle hosted urls in a nav context', function () {
|
2015-09-26 00:31:54 +03:00
|
|
|
rendered = helpers.url.call(
|
2017-04-03 18:29:36 +03:00
|
|
|
{url: 'http://localhost:82832/qux', label: 'Qux', slug: 'qux', current: true},
|
2015-01-28 08:57:19 +03:00
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-04-03 18:29:36 +03:00
|
|
|
rendered.string.should.equal('http://localhost:82832/qux');
|
2015-01-28 08:57:19 +03:00
|
|
|
});
|
|
|
|
|
2016-01-05 21:04:39 +03:00
|
|
|
it('should handle hosted urls in a nav context with secure', function () {
|
|
|
|
rendered = helpers.url.call(
|
2017-03-21 11:24:11 +03:00
|
|
|
{
|
2017-04-03 18:29:36 +03:00
|
|
|
url: 'http://localhost:82832/qux', label: 'Qux', slug: 'qux', current: true,
|
2017-03-21 11:24:11 +03:00
|
|
|
secure: true
|
|
|
|
},
|
2016-01-05 21:04:39 +03:00
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-04-03 18:29:36 +03:00
|
|
|
rendered.string.should.equal('https://localhost:82832/qux');
|
2016-01-05 21:04:39 +03:00
|
|
|
});
|
|
|
|
|
|
|
|
it('should handle hosted https urls in a nav context with secure', function () {
|
|
|
|
rendered = helpers.url.call(
|
2017-03-21 11:24:11 +03:00
|
|
|
{
|
2017-04-03 18:29:36 +03:00
|
|
|
url: 'https://localhost:82832/qux', label: 'Qux', slug: 'qux', current: true,
|
2017-03-21 11:24:11 +03:00
|
|
|
secure: true
|
|
|
|
},
|
2016-01-05 21:04:39 +03:00
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-04-03 18:29:36 +03:00
|
|
|
rendered.string.should.equal('https://localhost:82832/qux');
|
2016-01-05 21:04:39 +03:00
|
|
|
});
|
|
|
|
|
2015-01-28 08:57:19 +03:00
|
|
|
it('should handle hosted urls with the wrong protocol in a nav context', function () {
|
2015-09-26 00:31:54 +03:00
|
|
|
rendered = helpers.url.call(
|
2017-04-03 18:29:36 +03:00
|
|
|
{url: 'https://localhost:82832/quux', label: 'Quux', slug: 'quux', current: true},
|
2015-01-28 08:57:19 +03:00
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-04-03 18:29:36 +03:00
|
|
|
rendered.string.should.equal('http://localhost:82832/quux');
|
2015-01-28 08:57:19 +03:00
|
|
|
});
|
|
|
|
|
2015-09-26 00:31:54 +03:00
|
|
|
it('should pass through protocol-less URLs regardless of absolute setting', function () {
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: '//casper.website/baz', label: 'Baz', slug: 'baz', current: true},
|
|
|
|
{hash: {}});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('//casper.website/baz');
|
2015-01-28 08:57:19 +03:00
|
|
|
|
2015-09-26 00:31:54 +03:00
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: '//casper.website/baz', label: 'Baz', slug: 'baz', current: true},
|
2015-01-28 08:57:19 +03:00
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('//casper.website/baz');
|
2015-01-28 08:57:19 +03:00
|
|
|
});
|
2015-02-13 02:09:12 +03:00
|
|
|
|
2015-09-26 00:31:54 +03:00
|
|
|
it('should pass through URLs with alternative schemes regardless of absolute setting', function () {
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: 'tel:01234567890', label: 'Baz', slug: 'baz', current: true},
|
|
|
|
{hash: {}});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('tel:01234567890');
|
2015-09-26 00:31:54 +03:00
|
|
|
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: 'mailto:example@ghost.org', label: 'Baz', slug: 'baz', current: true},
|
|
|
|
{hash: {}});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('mailto:example@ghost.org');
|
2015-09-26 00:31:54 +03:00
|
|
|
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: 'tel:01234567890', label: 'Baz', slug: 'baz', current: true},
|
2015-02-13 02:09:12 +03:00
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('tel:01234567890');
|
2015-09-26 00:31:54 +03:00
|
|
|
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: 'mailto:example@ghost.org', label: 'Baz', slug: 'baz', current: true},
|
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('mailto:example@ghost.org');
|
2015-09-26 00:31:54 +03:00
|
|
|
});
|
|
|
|
|
|
|
|
it('should pass through anchor-only URLs regardless of absolute setting', function () {
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: '#thatsthegoodstuff', label: 'Baz', slug: 'baz', current: true},
|
|
|
|
{hash: {}});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('#thatsthegoodstuff');
|
2015-09-26 00:31:54 +03:00
|
|
|
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: '#thatsthegoodstuff', label: 'Baz', slug: 'baz', current: true},
|
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('#thatsthegoodstuff');
|
|
|
|
});
|
|
|
|
|
|
|
|
it('should not HTML-escape URLs', function () {
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: '/foo?foo=bar&baz=qux', label: 'Foo', slug: 'foo', current: true});
|
|
|
|
should.exist(rendered);
|
|
|
|
rendered.string.should.equal('/foo?foo=bar&baz=qux');
|
|
|
|
});
|
|
|
|
|
|
|
|
it('should encode URLs', function () {
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: '/foo?foo=bar&baz=qux&<script>alert("gotcha")</script>', label: 'Foo', slug: 'foo', current: true});
|
|
|
|
should.exist(rendered);
|
|
|
|
rendered.string.should.equal('/foo?foo=bar&baz=qux&%3Cscript%3Ealert(%22gotcha%22)%3C/script%3E');
|
|
|
|
});
|
|
|
|
|
|
|
|
it('should not double-encode URLs', function () {
|
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: '/?foo=space%20bar', label: 'Foo', slug: 'foo', current: true});
|
|
|
|
should.exist(rendered);
|
|
|
|
rendered.string.should.equal('/?foo=space%20bar');
|
2015-02-13 02:09:12 +03:00
|
|
|
});
|
2015-09-23 18:40:06 +03:00
|
|
|
|
2015-09-26 00:31:54 +03:00
|
|
|
describe('with subdir', function () {
|
|
|
|
it('external urls should be retained in a nav context with subdir', function () {
|
2017-04-03 18:29:36 +03:00
|
|
|
configUtils.set({url: 'http://localhost:82832/blog'});
|
2015-09-26 00:31:54 +03:00
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: 'http://casper.website/baz', label: 'Baz', slug: 'baz', current: true},
|
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-01-11 13:45:56 +03:00
|
|
|
rendered.string.should.equal('http://casper.website/baz');
|
2015-09-26 00:31:54 +03:00
|
|
|
});
|
2015-09-23 18:40:06 +03:00
|
|
|
|
2015-09-26 00:31:54 +03:00
|
|
|
it('should handle subdir being set in nav context', function () {
|
2017-04-03 18:29:36 +03:00
|
|
|
configUtils.set({url: 'http://localhost:82832/blog'});
|
2015-09-23 18:40:06 +03:00
|
|
|
|
2015-09-26 00:31:54 +03:00
|
|
|
rendered = helpers.url.call(
|
|
|
|
{url: '/xyzzy', label: 'xyzzy', slug: 'xyzzy', current: true},
|
|
|
|
{hash: {absolute: 'true'}});
|
|
|
|
should.exist(rendered);
|
2017-04-03 18:29:36 +03:00
|
|
|
rendered.string.should.equal('http://localhost:82832/blog/xyzzy');
|
2015-09-26 00:31:54 +03:00
|
|
|
});
|
|
|
|
});
|
2014-10-10 18:54:07 +04:00
|
|
|
});
|