@atomist/rug - npm Package Versions

[1.0.0-m.7] - 2017-08-24

Milestone 7 release

Changed

• Avoid TypeScript keywords in function parameter names [#664][664] and clean up generated TypeScript

[1.0.0-m.6] - 2017-08-17

Milestone 6 (tweaks) release

Added

• Can now set parameterName on IdentifiableInstruction in Directed/Response Messages for use in select boxes
• Parameter and MappedParameter decorated properties from super classes are now inherited by sub-classes [#646][646]
• Added GITHUB_DEFAULT_REPO_VISIBILITY mapped parameter that determines repository visibility based on organization GitHub plan
• MappedParameters.{CORRELATION_ID,GITHUB_URL} in TypeScript

Changed

• Updated typescript & typedoc used for doc generation to 2.4.1 and 0.7.1 respectively
• Added post property to UpdatableMessage to indicate if we message should be written if it didn't previously existed
• Leave timestamp undefined when creating UpdatableMessage [#654][654]
• Export LocallyRenderedMessage in TypeScript

Fixed

• Slice with out-of-bounds numbers works OK in JS, so we should allow them here instead of failing with exceptions.
• Ensure default values for optional parameters to Rug Functions are used, instead of null. Primitives are converted to 0 or false

[1.0.0-m.5] - 2017-07-11

Milestone 5 (Summer) release

Added

• Added new UpdatableMessage to allow messages to be re-written in the bot

Changed

• BREAKING Removed all usage of Scala Future in PlanRunner and corresponding APIs
• Updated JavaParser to 3.2.8
• Updated artifact-source to 1.0.0-m.5

Fixed

• Ensure index and original array are also passed to map callback functions [#632][632]
• Now only load Gherkin feature definitions from the .atomist/tests directory [#629][629]

[1.0.0-m.4] - 2017-06-01

Milestone 4 (whiskey) release

Added

• Add internal support for Scope on Rugs. Currently this is only used on Response Handlers, and will be used to change the visibility of auto-generated ones so they are not indexed, displayed etc by the CLI or Bot.
• Add support for @IntegrationTest decorator. TypeScript Classes with this decorator will behave much like Command Handlers, except in that they will have additional metadata allowing the CLI or runtime to behave differently when required.
• Exposed underlying TypeScript class decorator logic so that they can be called directly to emit Rugs programmatically [#595][595]
• Allow commitMessage to be set on Edit instructions [#593][593]
• Ability to implement the startingPoint method in a generator to start with an empty repo or the content of a Git repo, if the runtime permits.
• Added HandlerContext as second parameter to ResponseHandler.handle invocations [#587][587]
• Added Identifiable instruction that can be used for DirectedMessage and ResponseMessage
• Rug Language Extensions can provide a preprocessing (and postprocessing) step. This lets them do string manipulation before parsing, and undo it afterward.

Changed

• BREAKING Removed support for Velocity templates from Project
• Allow editWith and generateWith calls in Gherkin tests without parameters
• Parameters passed to ResponseHandlers with no declared parameters are now set directly on the instance. This can be used to avoid using @Parameter declarations
• Handle project generate failures
• BREAKING remove ProjectEditor & ProjectGenerator interfaces. This also removes support for legacy parameter[] Parameter declarations
• BREAKING remove tags from Parameters (they are unused)
• Remove some more remnants of reviewers
• Harmonized much of the Rug loading code between project operations and handlers
• RugLanguageExtensions may return a smaller interface, ParsedNode from their parsing method fileToRawNode, instead of requiring PositionedTreeNode
• Removed CommonViewOperations with its deprecated fail and println methods
• Removed unnecessary InstantEditorFailureException as TypeScript can throw errors

Fixed

• Decorators now hide defined properties by setting enumerable=false [#554][554]
• Fixed handling of fields set with Object.defineProperty (now enumerable)
• @Editor, @Generator, and @EventHandler decorators now allow 'name' to be omitted. If you omit the name, it uses the name of the class.
• files in ProjectView now returns a list of FileMutableView [#623][623]

[1.0.0-m.3] - 2017-05-09

May milestone 3 release

Added

• pathExpressionEngine and contextRoot now available within event handlers
• BREAKING Added ability to specific target of an Edit Instruction so that source/target branches, title and body can be specified. Breaks the ProjectManagement Scala interface only.
• Added ability to indicate in TypeScript generated interfaces when a JVM method being exposed is marked as @Deprecated
• Ability to test when a scenario aborts [#569][569]
• Types to Gherkin well-known step callback signatures [#574][574]

Changed

• Standardize use of Object.defineProperty in TypeScript decorators
• If the first parameter to a Rug Kind TypeScript decorator is omitted, the constructor's name is used instead. E.g. it is now possible to declare a command handler with: @CommandHandler("description only")
• BREAKING Gherkin handler step 'parameters were invalid' renamed to 'handler parameters were invalid' [#566][566]
• BREAKING Removed Spring and Spring project types, these don't belong in rug and will resurface in a separate project
• Add instructions to DirectedMessage and ResponseMessage
• Add optional id to Presentable instruction
• Missing implementations of Given and When steps now are returned as NotYetImplemented in testing results [#570][570]

Fixed

• Improve archive loading performance by creating new ArtifactSource with only Rug content, instead of filtering all files in original archive
• Throw exceptions if there is more than one Rug with the same name in an archive [#561][561]
• Fix StackOverflow when calling toString on LinkableContainerTreeNode, can't recurse as this is a graph not a tree.
• Remove node_modules from TypeScript sources path [#442][442]

[1.0.0-m.2] - 2017-04-26

Initial milestone 2 release

Changed

• Fix NPM publish for milestone and release candidate releases
• Consolidate NPM publish for dev and release versions

[1.0.0-m.1] - 2017-04-26

Initial milestone 1 release

Added

• Support for cloning a repo from GitHub in Gherkin tests, via ScenarioWorld

Changed

• BREAKING TypeScript Match now uses property access, not function
• Updated all Atomist dependencies to 1.0.0-m.1 versions
• Handlers are now picked up from arrays as well as regular vars

Fixed

• project.findFile now works on paths starting with a '/' [#523][523]
• Rug Function exceptions are now passed to error handlers. Maybe: Response now passed to handlers when unknown Rug Functions are encountered [#536][536]

[0.26.1] - 2017-04-24

Secret release

Added

• Added support for resolution of Secrets from Event Handlers. NOTE: it's up to secret resolver implementations to make sense of what this means in the particular context!

Changed

• Improved JVM toString behavior for JavaScript proxies
• Added reducer to allow JSON.stringify to be used with JVM-backed nodes

[0.26.0] - 2017-04-21

Election Release

Added

• Added ability to resolve Project objects from Repo or Commit, if a RepoResolver is provided by the runtime
• Added Impact object to enable drilling into the changes in a Push in a path expression, extracting old and new files.
• Added stringify function on TreeHelper.ts to help dump hierarchy of AST nodes when debugging.
• jsSafeCommittingProxy now returns undefined on unknown properties on dynamic nodes rather than throwing an exceptions

Changed

• Response.Status of instructions whose failure is handled by a ResponseHandler now have a status of Handled instead of Failed
• BREAKING Event and Command Handlers must return EventPlan and CommandPlan respectively to remove confusion as to the different capabilities
• Project test steps can now return void, as for handlers.

[0.25.3] - 2017-04-13

Parameter release

Changed

• Parameter decorator now takes a copy of the parameter configuration. It was overwriting its contents.