rlang  Sun, 24 Nov 2019 09:48:37 +0000

Modified page: https://wiki.horde.org/Doc/Dev/HordeYmlFormat
New Revision:  3
Change log:  syntax

@@ -24,8 +24,9 @@
 license: identifier: An SPDX license identifier string
 license: uri: a link to a fulltext license

 Example:
+
 <code>
 ---
 id: Db
 name: Db
@@ -98,24 +99,24 @@
       PDO: '*'
 </ccode>

 ++ Additions for transitioning to composer based installs
-
+
optional top level key "autoload", inspired by corresponding composer.yml structure
 It hints how autoloaders should expect to find php classes from the package.
-
+
 Structure:
 autoload: psr-0: list of "Class_Prefix" : "dir"
 autoload: psr-4: list of "\\Prefix" : "dir"
-
-
-autoload: classmap: list of directories to recursively scan for php files containing classes
+
+
+autoload: classmap: list of directories to recursively scan for php files containing classes

 <code>
 autoload:
   classmap: ['lib/']
-</code>
-
+</code>
+
 The default if absent would be equivalent to psr-0: "Horde_Foo": /Lib

 +++ Composer native dependency definitions

@@ -139,8 +140,9 @@
By default, the composer.json writer will treat all executable files living directly under package/bin as vendor binaries.
 This can be overridden:
commands: optional: List of paths relative to package root which should be offered as vendor binaries. If you provide commands, no automatic search in bin/ will happen. nocommands: optional: List of paths relative to package root which should not be offered as vendor binaries. nocommands wins over commands list or implicitly found bin/
+
 <code>
 nocommands:
   - 'bin/horde-bootstrap'
-<code>
+</code>

--
commits mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]

Reply via email to