Sha256: 87812b93e2e65da8a062a7175ea1c55edc43a738d68419291f3647fdf38ad7ab
Contents?: true
Size: 1.35 KB
Versions: 7
Compression:
Stored size: 1.35 KB
Contents
Feature: MooForge compatibility layer
In order to be compliant with mooforge packages, we should accept
various quirky source files.
Scenario: Compiling a mooforge package that uses mooforge tag dependency notation
When I run "jsus MooforgePlugin/Plugin tmp -d MooforgePlugin/Core"
Then the following files should exist:
| tmp/plugin.js |
And file "tmp/plugin.js" should contain
"""
/*
---
script: Core.js
description: Mootools fake core
license: MIT-style license
authors:
- Valerio Proietti
provides: [Core]
...
*/
"""
And file "tmp/plugin.js" should contain
"""
/*
---
script: plugin.js
description: plugin main file
license: UNLICENSE
authors:
- Mark Abramov
provides:
- Base
requires:
- /Support
- mootools_core/1.3.0: Core
...
*/
"""
And file "tmp/plugin.js" should contain
"""
/*
---
script: plugin-support.js
description: plugin support file
license: UNLICENSE
authors:
- Mark Abramov
provides:
- Support
requires:
- mootools_core/1.3.0: Core
...
*/
"""
And file "tmp/plugin.js" should have "script: plugin-support.js" before "script: plugin.js"
Version data entries
7 entries across 7 versions & 1 rubygems