[ROADMAP] Specification Version 2.0 // UI5 CLI 2.0

RandomByte commented 4 years ago

This is a list of possible changes that might be implemented with UI5 CLI 2.0. It is not final. Feedback is appreciated.

Current master branches of all UI5 Tooling repositories (except UI5 Tooling) reflect v2.0 development.

Specification Version 2.0

specVersion: '2.0'

[x] Schema validation of ui5.yaml: UI5 Project will error out for unrecognized fields or wrong values (https://github.com/SAP/ui5-project/pull/274)
[x] Require namespace for application and library projects: UI5 Project must be able to determine the projects namespace. E.g. through the manifest.json or .library file (https://github.com/SAP/ui5-builder/pull/430/files)
- A manual configuration in the ui5.yaml is not allowed. This is to make sure that UI5 runtime also has access to it
[x] By default, .properties files are assumed to be UTF-8 encoded instead of ISO-8859-1 (documentation)

[ ] (possibly 3.0) Going forward, there are separate Specification Versions for Extensions and Projects as outlined here: https://github.com/SAP/ui5-project/issues/167
[x] New metadata attributes deprecated ~and restricted~ will display warnings when such a project is used as a direct dependency (https://github.com/SAP/ui5-project/pull/268)

@ui5/cli@2.0

[x] Drop support for Node.js Version <10 ~(or possibly <12)~: Node.js 8 and 9 are EOL
- Various dependencies require Node.js 10 now
[x] Remove export of all sub-modules from each UI5-modules index.js: Synchronous require of unneeded modules is bad for performance. Example
- ~Alternative to be discussed~~
- ➡️ Implemented lazy requires in all index.js
[x] Remove synchronous export of all tasks in UI5 Builder taskRepository
[x] Remove deprecated useNamespaces parameter from UI5 Project resourceFactory.createCollectionsForTree API (https://github.com/SAP/ui5-fs/pull/223)
[x] Bump Yargs