Package Exports

essupernext

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (essupernext) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

essupernext

ES2018 a.k.a. "ESSuper-Next". Dot-syntax and keyword conversion.

Handy DIY compiler for dot syntax to get your code ready for ES2018.

Usage

npm install -g essupernext
essupernext index.js

Example output

(GitHub, stupidly, doesn't support proper highlighting for ES2018, so this will look off. Still tonnes more readable though!)

c joi . require.'joi'.
c commentsDb . require.'connection-mongo'..'comments'.
c ObjectId . require.'connection-mongo'..ObjectId
c remit . require.'connection-remit'.
c log . require.'connection-logger'.
c validate . require.'service-helpers'..remit. log..validate

m.exports . .. .. .
  remit.res.'comments.create'. .
    validate.joi.object...keys..
      user: joi.string...trim...regex./^.0-9a-fA-F..24.$/..required...
      content: joi.string...trim...regex./^.0-9a-fA-F..24.$/..
      task: joi.string...trim...regex./^.0-9a-fA-F..24.$/..
      comment: joi.string...trim...required..
    ...xor.'content'. 'task'...

    createComment
  ..
.

f createComment .args. done. .
  l doc . .
    user: ObjectId.args.parsed.user..
    comment: args.parsed.comment
  .

  if .args.parsed.content. .
    doc.content . ObjectId.args.parsed.content.
  . else .
    doc.task . ObjectId.args.parsed.task.
  .

  commentsDb
    .collection.'comments'.
    .insertOne.doc. .err. result. .. .
      if .err. .
        log.error.new E.err..

        r done.err.
      .

      if .result.insertedCount. .
        remit.emit.'comments.created'. result.ops.0..
      .

      r done.null. result.ops.0..
    ..
.