- Source:
Configuration-based functionality.
Methods
ish.config(oConfig) → {function}
- Source:
Creates an interface that merges the content of the passed options into the underlying configuration, overriding any original values.
Example
When used internally for ish
mixins, the recommended pattern to setup a related ish.config
entry is:
ish.config.mixinPath = ish.config({ some: "mixin configuration value" });
Parameters:
Name |
Type |
Description |
oConfig |
object
|
Object that stores the underlying configuration values. |
Returns:
Type |
Description |
function
|
Function that manages and returns the object representing the configuration values. |
ish.config.ish(oOptionsopt) → {object}
- Source:
ish.js configuration values.
Parameters:
Name |
Type |
Attributes |
Description |
oOptions |
object
|
<optional>
|
Value representing the updated configuration values. |
Returns:
Type |
Description |
object
|
Value representing ish.js's configuration values. |
ish.config.require(oOptionsopt) → {object}
- Source:
ish.require
configuration values.
Parameters:
Name |
Type |
Attributes |
Description |
oOptions |
object
|
<optional>
|
Value representing the updated configuration values. |
Returns:
Type |
Description |
object
|
Value representing ish.require 's configuration values. |
[mixin]
ish.config.type.date(oOptionsopt) → {object}
- Source:
ish.type.date
configuration values.
From Mixin: ish.type.date-format.js
must be included for ishJS
to access this functionality.
Parameters:
Name |
Type |
Attributes |
Description |
oOptions |
object
|
<optional>
|
Value representing the updated configuration values. |
Returns:
Type |
Description |
object
|
Value representing ish.type.date 's configuration values. |