SAP / ui5-builder / 212 / 2

95%

main: 95%

push

travis-ci

[INTERNAL] Create and integrate a new task 'generateLibraryManifest' (#26)

The task creates a manifest.json file for libraries that don't have one.
It collects the necessary information from the project structure
(supported themes, versions of dependencies), from the .library file
(name, dependencies, supported themes, thirdparty components, i18n
information...) and from an initLibrary call inside the library.js file
(implemented controls, elements, types and interfaces, noLibraryCSS
flag).

An existing manifest.json won't be modified or overwritten.

- refactor test scenario 'library.h' so that the sub-components reside
  in the namespace of the library
- add new test scenario 'library.i' to test manifest creation with 
  data from .library and library.js file
- add the newly generated manifest.json to the expected content of 
  the other library test scenarios
- enhance all library test scenarios with a dependency to a fake 
  'sap.ui.core' lib. For UI5 libs, this dependency is mandatory and 
  manifest generation needs it to determine the UI5 version
- re-classify log message for missing .library file as 'verbose'

180 of 344 branches covered (52.33%)

Branch coverage included in aggregate %.

622 of 858 relevant lines covered (72.49%)

7.22 hits per line