Changelog

1.2.1 - 2018-11-05

Whats new?

@marblejs/core - fixed an issue with missing chalk dependency (issue: #77)

1.2.0 - 2018-11-05

Whats new?

@marblejs/middleware-logger - extended available API (see: middleware-logger chapter)
@marblejs/core - Corrected nullable values detection inside Maybe monad

From version v1.2 the logger$ entry point is marked as deprecated. Use loggerWithOpts$ instead. From the version v2.x the old entry point will be swapped with newer implementation

1.1.1 - 2018-10-21

Whats new?

@marblejs/core resolves #67 (path matching for trailing slash combined with wildcard parameter)

1.1.0 - 2018-09-29

10 days ago we've got an official v1.0.0 release - this time we have another cool news to share with you!

Whats new?

Introducing new package @marblejs/middleware-jwt - a HTTP requests authentication middleware based on JWT mechanism. 🚀 🎉 For more API reference please visit our official documentation.
Resolved an issue in the scenario when the grouped middleware throws an error (eg. when request is not authorized) and connected Effect endpoint unexpectedly catches the thrown error. See more details please visit #73
Support for TypeScript v3.1.x
[internal] - Moved back from webpack to well-tested tsc compiler which makes our build artifacts more predictable and less error prone

1.0.0 - 2018-09-18

1.0.0-rc.3 - 2018-09-17

Whats new?

Integration with path-to-regexp library
Support for wildcard parameter, eg. /foo/:param*. For more details see: example implementation

const getFile$ = EffectFactory
  .matchPath('/:dir*')
  .matchType('GET')
  .use(req$ => req$
    .pipe(
      map(req => req.params.dir as string),
      switchMap(readFile(STATIC_PATH)),
      map(body => ({ body }))
    ));

Fixed a problem with incorrectly generated declaration files for @marblejs/middleware-joi package.

1.0.0-rc.2 - 2018-09-10

pre-release

Whats new?

Fixed problem with incorrectly concatenated wildcard endpoint when combined with parametrized route.

const notFound$ = EffectFactory
  .matchPath('*')
  .matchType('*')
  .use(req$ => req$.pipe(
    switchMap(() =>
      throwError(new HttpError('Route not found', HttpStatus.NOT_FOUND))
    )
  ));

export const api$ = combineRoutes(
  '/api/:version',
  [ notFound$ ],
);

For non-TypeScript developers there was no validation made during app startup, eg. EffectFactory methods were not validated if developer provided wrong HTTP method to the matchType. Going to the expectations we introduced dedicated CoreError type used for throwing an package related error messages, eg. for notifying non-TypeScript developers if they made a mistake in the method arguments.

TypeScript v.3.0.x support
RxJS v6.2.2 support
Lerna v3.3.0 support
Introduced Webpack based build process - from now builds are optimized and properly compressed

1.0.0-rc.1 - 2018-08-14

pre-release

Breaking changes:

Changed httpListener error handler attribute from errorMiddleware 👉 errorEffect. There was an inconsistency with previous error handler definition and naming. We had to correct this because error handler acts as an Effect instead of Middleware.

Old bootstrapping API:

const app = httpListener({
  middlewares,
  effects,
  errorMiddleware,  👈
});

New bootstrapping API:

const app = httpListener({
  middlewares,
  effects,
  errorEffect,  👈
});

Whats new?

Exposed res.send method - from now you don't have to send response manually via dedicated Node.js http.OutgoingMessage API. The res.send method returns an empty stream, thus it can be easily composed inside middleware pipeline.

const middleware$: Middleware = (req$, res) =>
  req$.pipe(
    switchMap(() => res.send({ body: 💩, status: 304, headers: /* ... */ }),
  );

Exposed type aliases for common Marble.js architectural blocks:

const effect$: Effect = req$ =>
  req$.pipe(
    // ...
  );

const middleware$: Middleware = (req$, res) =>
  req$.pipe(
    // ...
  );

const error$: ErrorEffect = (req$, res, err) =>
  req$.pipe(
    // ...
  );

1.0.0-rc.0 - 2018-07-07

pre-release

Breaking changes

In order to factorize the routing table statically, we need to introduce the breaking change in Effect API definition.

Old Effect API:

const getUsers$: Effect = request$ =>
  request$.pipe(
    matchPath('/'),
    matchType('GET'),
    // ...
  );

New Effect API:

const getUsers$ = EffectFactory
  .matchPath('/')
  .matchType('GET')
  .use(req$ => req$.pipe(
    // ...
  ));

separately imported matchPath and matchType stream operators are removed and are part of EffectFactory instead.

Whats new?

@marblejs/core - internals - refactored + rebuilt routing resolving mechanism. Thanks to the latest changes we gained hudge performance boost.
@marblejs/core - internals - improved performance for middleware resolving flow
@marblejs/core - internals - rewritten URL params intercepting mechanism
@marblejs/middleware-body - added support for x-www-form-urlencoded Content-Type

0.5.0 - 2018-06-13

pre-release

Fixes

corrected @marblejs/middleware-logger response time logging (issue: #48)

Whats new?

combineRoutes() API allows to compose middlewares for grouped routes (feature request: #36) (see docs)

0.4.2 - 2018-06-10

pre-release

Fixes

fixed an issue with not matched routes in case of reordered matchType and matchPathoperators for the same routes but with different methods (PR #46)

0.4.1 - 2018-06-03

pre-release

Fixes

resolved an issue with TypeScript compiler flag responsible for strict function types (issue: #43)
added support for TypeScript v2.9.1

0.4.0 - 2018-05-31

pre-release

Fixes

fixed an issue with Effects matching hazard (issue: #35)

Whats new?

ability to create 404 handlers using matchType('*') and matchPath('*') (issue: #27)
HttpError constructor now can take data: object as optional third argument

0.3.2 - 2018-05-29

pre-release

Fixes

support for non-JSON Effect return types (issue: #33) Thanks @couzic!

Whats new?

mime-type / content-type auto detection

0.3.1 - 2018-05-27

pre-release

Fixes

corrected peerDependency versions for @marblejs/* packages

0.3.0 - 2018-05-27

pre-release

Breaking changes

moved bodyParser$ and logger$ middleware outside @marblejs/core to separete@marblejs/middleware-body and @marblejs/middleware-logger packages

Whats new?

added support for intercepting path parameters req.params (see: Routing chapter)
added support for intercepting query parameters req.query (see: Routing chapter)
ability to compose middlewares inside Effect request pipeline via use operator (see: Middlewares chapter)
new middleware @marblejs/middleware-joi - a Joi validation middleware
minor bugfixes and code improvements

0.2.x - 2018-05-14

pre-release

Initial pre-release version

PreviousFAQ

Last updated 5 years ago