For frequently changing external files (libraries, widgets...) which do not follow the mootools package-syntax and have no description-header in their files, I added the ability to describe the components of a file in the manifest file.
license: "MIT License"
copyright: "© MooTools"
authors: "MooTools Development Team"
- name: Array
description: Contains Array Prototypes like each, contains, and erase.
license: MIT-style license.
Having the description in the manifest the actual source file doesn't need a header.
I decided to handle the file path and the description in an array with 2 elements, but it may also be possible and maybe easier to read if you handle that in a map using the file path as key and the description map as value?!
Added the ability to read the description for a file from the source-…
…entry in the manifest.