loopback-boot/test/fixtures/simple-app
Raymond Feng 2f72006c88 Implement shorthand notation for middleware paths
When the middleware name (path) is in the format {module}#{filename},
loopback-boot resolves the path by trying multiple locations and
using the first one that exists:

 - {module} and check the {filename} property of the exports
     -> e.g. loopback.rest
- {module}/server/middleware/{filename}
    -> e.g. loopback/server/middleware/rest
 - {module}/middleware/{filename}
    -> e.g. loopback/middleware/rest

Values in any other format will bypass this resolution algorithm and
they will be used in the original form:

 - a full path in a module: loopback/server/middleware/rest
 - a relative path: ./middleware/custom, ./custom, ../logger
 - an absolute path: /usr/local/lib/node_modules/compression
2014-11-25 11:43:00 +01:00
..
boot Add jscs style check, fix violations found 2014-11-13 15:54:59 +01:00
client Implement shorthand notation for middleware paths 2014-11-25 11:43:00 +01:00
middleware Implement shorthand notation for middleware paths 2014-11-25 11:43:00 +01:00
node_modules/my-module Implement shorthand notation for middleware paths 2014-11-25 11:43:00 +01:00
config.json Rename `app.json` to `config.json` 2014-06-25 08:18:04 +02:00
datasources.json Initial implementation 2014-05-23 16:50:40 +02:00
middleware.json Load middleware and phases from `middleware.json` 2014-11-19 09:45:04 +01:00
model-config.json Rename `models.json` to `model-config.json` 2014-07-15 11:09:39 +02:00