Investigate options to reduce boiler plate in Typescript rugs

[kipz]

Currently there are many imports, quite a few annotations and some verbose APIs.

There are many options here, including wildcard imports, improved APIs, increased use of conventions etc.

[Lawouach]

Tradeoff between readability/reducing noise vs engineering best practices indeed.

[kipz]

imports could be produced by generating an aggregate module containing just exports, but would mean that a little more in terms of each use:

import * as atomist from '@atomist/rug/All'

val foo: atomist.File = null

But this has the obvious drawback that we'll have to rev this aggregate when any of the core types change, and as we move those types out of Rug library itself, that'll become even more difficult to manage.

[kipz]

The below looks nice. It's removed any weird duplication due to the way decorators work, and provides a simple way to lookup services like the PathExpressionEngine.

import {SimpleEditor} from "./ProjectEditor"
import {Project} from "../model/Core"
import {Parameter} from "./Parameters"
import {PathExpressionEngine} from "../tree/PathExpression"
import {Result,Status} from "./Result"
import {Registry} from "./Registry"

let editor: SimpleEditor = {
  name: "HelloWorld",
  description: "Much simpler API for editors",
  parameters: [{name: "content", pattern: "^.*$", required: true, description: "Simple content param"}],
  edit: (project: Project, {content} : {content: string}) => {
    //codes here
    let engine: PathExpressionEngine = project.context().pathExpressionEngine()
    return new Result(Status.Success, "Woot")
  }
}