-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[BREAKING] Schema: Restrict metadata.name for specVersion >= 3.0
As proposed in chapter 6 of RFC0012([1]), restrict the 'name' property for projects and extensions defining specification version 3.0 and later. BREAKING CHANGE: For projects and extensions defining specVersion 3.0 and later, the metadata.name property must satisfy the following conditions: * Must be at least 3 characters long * Must be no longer than 50 characters * Must contain lowercase characters only * Must contain alphanumeric characters, dash, underscore and period only - Exception: `@` and `/` are allowed at certain positions as explained below * Must start with an alphabetic character or an `@`-character * If a name starts with an `@`-character, it must contain exactly one forward-slash `/` - This is aligned with the npm concept for package scopes - e.g. `@org/lib.name` For details, please see refer to chapter 6 of RFC0012([1]). [1]: SAP/ui5-tooling#664
- Loading branch information
1 parent
cf96b6f
commit 3fde053
Showing
18 changed files
with
670 additions
and
107 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.