Sha256: cd88f3bf2dfeb39aa932f28380285d3f916fcc90c7d4f8e62cada48f7b317793
Contents?: true
Size: 1.3 KB
Versions: 2
Compression:
Stored size: 1.3 KB
Contents
Feature: extensions In order to monkeypatch other libraries, I should be able to cook some extensions. Scenario: monkeypatch for external dependency When I run "jsus -i Extensions -o tmp -d Extensions/Mootools" Then the following files should exist: | tmp/package.js | And file "tmp/package.js" should contain """ /* --- script: Core.js description: Mootools fake core license: MIT-style license authors: - Valerio Proietti provides: [Core] ... */ """ And file "tmp/package.js" should contain """ /* --- script: MootooolsCore.js description: Extension for mootools core license: MIT-style license authors: - Mark Abramov extends: Mootools/Core ... */ """ And file "tmp/package.js" should contain """ /* --- script: Color.js description: A library to work with colors license: MIT-style license authors: - Valerio Proietti requires: - Mootools/Core provides: [Color] ... */ """ And file "tmp/package.js" should have "MootooolsCore.js" after "script: Core.js" And file "tmp/package.js" should have "MootooolsCore.js" before "script: Color.js"
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
jsus-0.2.2 | features/command-line/extensions.feature |
jsus-0.2.1 | features/command-line/extensions.feature |