xtypejs Extension - Type Name Utilities
npm install xtypejs-extension-typename-utilsxtype.util.nameToId
xtype.util.idToName
xtype.util.typeNames
xtype.util.typeIds
sh
npm install xtypejs-extension-typename-utils --save
`
$3
`js
var xtype = require('xtypejs');
var xtypejsTypeNameUtilsExtension = require('xtypejs-extension-typename-utils');
// The type name utility methods are NOT available here
xtype.ext.registerExtension(xtypejsTypeNameUtilsExtension);
// The type name utility methods are now available here
`
$3
Include the extension script after the xtypejs script to automatically register the extension into xtypejs without exporting any globals. This relies on xtypejs being available in the xtype global variable.
`html
`
If the extension script needs to be included before the xtypejs script, or the xtype global is not available (or is using a different variable name) when the extension script is included, the extension will be exported instead to a global variable named xtypejsTypeNameUtilsExtension, which must then be manually registered into xtypejs as an extension.
`html
`
$3
For usage, see:
xtype.util.nameToId - doc*
xtype.util.idToName - doc*
xtype.util.typeNames - doc*
xtype.util.typeIds - doc*
$3
If the HTML script tag was used to import the extension script in a browser environment and in the absence of xtypejs in the xtype global variable, the extension will be exported to a global variable named xtypejsTypeNameUtilsExtension. The noConflict method of the exported extension can be used to reassign the extension to a different namespace or variable name, and return the global xtypejsTypeNameUtilsExtension variable to its previous value prior to including the extension script.
`js
var myExtension = xtypejsTypeNameUtilsExtension.noConflict();
/*
* myExtension is now xtypejsTypeNameUtilsExtension, while
* xtypejsTypeNameUtilsExtension variable is now returned to
* its original value prior to inclusion of the extension script.
*/
``